More about Hugo & hugodown

Read the manual πŸ˜‰

You can read the whole hugodown docs and probably should especially as hugodown evolves.

Also read the docs of the theme you choose.

You might not need to read Hugo docs, that are much longer, much more overwhelming: you mostly only need to read Hugo docs when you need to tweak or customize a theme.

Follow developments? πŸ‘€

If you start using Hugo & hugodown for your website…

Contributing guide for your website ✏

Personal website: take notes to not forget what you tweaked, etc.

Collaborative website: even Hugo users might not know your website structure!

Where to get help? πŸ‘‹

Other Hugo themes πŸŽ’

Another R package: blogdown πŸ“¦

blogdown is an alternative to hugodown. It might be better for your needs if you need something more complex than what hugodown provides: e.g. there are two special scripts build.R and build2.R for running arbitrary code before and after building your website.

The comparison hugodown vs blogdown is outdated as of blogdown new version.

The blogdown book will soon be updated. In the meantime read the package docs + its source code including its changelog.

Follow RStudio blog.

Hugo and CMS πŸ’»

To give a less technical interface to a Hugo website, you could use a CMS, see for instance what Steph Locke set up in this website with Netlify CMS.

Hugo template development/tweaking πŸ”©

  • How I started: I needed to tweak one thing in an existing theme and I googled that thing; then I had to tweak one more thing; etc. Others might have built a theme from scratch.

  • Mike Dane’s tutorials

  • Threads indicating resources for beginners and the lack thereof: 2018, 2019

  • What you must know according to Steph Locke

  • More advanced