The process of upgrading versions of blogdown and blogdown's Hugo instance is fraught. Here are some investigations and tips.
This RStudio project uses the dopetrope theme with the latest CRAN version of blogdown (ver 1.9) ; blogdown::hugo_version() = 0.96.0
- RStudio IDE > Addins > Serve site (have blogdown package installed)
- RStudio IDE > Addins > New post (have blogdown package installed)
- Make modifications based on earlier .md files found in
content/blog
Make a copy of earlier content in content/portfolio; modify.
notes can be found in another README. For this sub-trial, I installed a separate (non-blogdwon) Hugo instance on my system so that I could investigate aspects of how the dopetrope theme has changed.
- This theme is not a perfect fit with blogdown. It seems to use some rather idiosyncratic markdown. In this way the Hugo command
hugo new posts/hello-world.md(or the Blogdown:RStudio > Addins > New post) doesn't follow the same markdown format as more standard Hugo Theme seem to prefer. But it seems to work file (in both Hugo "pure" and blogdown-hugo). Anyway, it is easy enough to modify based on the format of existing documents found withincontent/portfolioorcontent/blog
- To install this theme I used File > New Project > New Directory > Website using blogdown
- To identify the theme I plugged in the github usernamne/reponame naming convention via the wizard
- I then updated files based on customized content from the rfun github repo. Those file changes are documented in the version control history (i.e. early git commits) for this project. Those commit messages reference copying files from mope. Mope was an earlier attempt that basically consists the updated dopetrope themes plus the custom files found at the blogdown-rfun site.
There are many ways the Hugo and Blogdown could talk over each other. Here are a collection of check functions
more notes should go here