R Markdown versus bookdown about rmarkdown-website-tutorial HOT 1 CLOSED

Hi @cjlortie,

I've been using both options and I think that bookdown is simpler building-wise -->>> but publishing is trickier.

• With the websites, you develop/write content in .Rmds on a gh-pages branch -> knit .htmls -> and push and voila, it's online!
• With bookdown, you develop/write content on some (eg master) branch -> knit .htmls -> have to transfers the .html files to the gh-pages branch for publishing. This extra step can be done
  • option 2A: as described by Yihui using Travis CI: for:
  • option 2B: writing a script (in R/bash/something else) to copy html content from the first branch to the gh-pages branch.
  • option don't do this: in Finder copying files from your first branch somewhere else, switching to the gh-pages branch, pasting and pushing.

Option 2A is obviously cleaner and better, and although I've worked hackily (new word there) with Travis CI in the past, in 2 days I couldn't get this to work properly (I was so close but had to move on). Ultimately I opted for option 2B, making this _deploy.r script (borrowed from a script from Ben Best).

from rmarkdown-website-tutorial.