Last week I was writing up some thoughts on trying to understand how unexpected the high temperatures on June 28th in Portland, OR, were. (They hit 115°F!) My goal was to think through some quantitative reasoning based on statistics, and I used R to support my calculations. Today, I realized I should have been able to write that post up in Rmarkdown in RStudio and post it to my Jekyll site (hosted in Github) with graphs and computations so much more easily. So I sat down to try to figure it out.

I sat down in front of Google and quickly found two pages with helpful information.

The first was Johannes C. Hellmuth’s “Posting Rmarkdowns to your Jekyll website ”. It showed me what to add to the YAML header:

layout: post
title: title
author: author
date: YYYY-MM-DD
    variant: markdown_github
    preserve_yaml: true

The value ‘markdown_github’ for the ‘variant’ option works, but the post I wrote had different styling than my Jekyll instance.

Then Steven V. Miller’s “Two Helpful R Markdown/Jekyll Tips for an Easier Blogging Experience” showed me how to fix that issue. It also showed me how to integrate “knitting” with my local Jekyll site’s structure.

Noteable to me was Miller recommendation for ‘gfm’ (Github-flavored markdown) for the ‘variant’ value. When I made this change, my post looked exactly the way it should.

Miller also showed ways to set knitr options so images produced by R would be written in the place that Jekyll looks for them.

```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
knitr::opts_knit$set(base.dir = "/Users/userename/Documents/GitHub/", base.url = "/")
knitr::opts_chunk$set(fig.path = "assets/images/subdirectory-for-post/")


I’m planning to make a different iamge subdirectory each time I used Rmarkdown for a Jekyll post. This way I don’t need to worry about naming conventions and accidentally overwriting images I created from previous Rmarkdown posts.