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.
If you start using Hugo & hugodown for your website…
Watch development on GitHub of hugodown, of the theme?
Subscribe to the hugodown issues that are interesting to you?
Personal website: take notes to not forget what you tweaked, etc.
Collaborative website: even Hugo users might not know your website structure!
RStudio community forum (RMarkdown category)
If you start tweaking Hugo templates, Hugo forum
Hugo Academic has excellent docs.
You can build many different websites with Hugo Academic, see a few examples below. The theme is very versatile, and widely used in the R community.
|Yanina Bellini Saibene’s personal website|
|Personal website of Alison Presmanes Hill|
|“Communicating with R Markdown” workshop by Alison Hill|
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.
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.
What you must know according to Steph Locke
You don't need to know go to build Hugo themes imo.— Steph Locke (@TheStephLocke) June 24, 2020
Intermediate "Hugo" knowledge is needed, & is:
- filesystem inheritance
- iteration (range, where)
- scoping (with, site, params, . )
- scalars, slices (aka vectors) , and maps (aka lists)
- control logic (if, comparisons)
The advanced level for themes is probably:— Steph Locke (@TheStephLocke) June 24, 2020
- asset pipelines inc. Npm packages like postcss
- output formats (md, json etc) and extra layouts
- html & css advanced stuff
- data driven components ( data/ and get*() s)