hugo-blog

To publish R Markdown posts to a Hugo blog, author content in `.rmd` files and render them to Hugo-compatible `.md` files. This workflow enforces strict YAML front matter conventions, including required fields like `output: hugodown::md_document`, correct slug and date formatting, and appropriate summary metadata.

Hugo blog series management requires creating source files with a strict naming convention: `{series_name}_part_{NN}.rmd` using zero-padded numbering. New series must start at `_part_01`, ensuring correct sequential structure and front matter organization for your generated posts.

The correct workflow to render R Markdown involves a dual-file system where you author in `content/posts/*.rmd` and render to `content/posts/*.md`. You must validate the md-format prior to rendering, configure hugodown output, and never edit the generated markdown output directly.

Yes, you need to update the repository README before pushing Hugo posts to Netlify. This pre-push process requires synchronizing the README post counters and series tables, ensuring the repository stays in sync with published content before committing both `.rmd` and `.md` files.

While Hugo blog publishing supports Quarto alongside R Markdown and hugodown, the enforced workflow specifically requires rendering `.rmd` files to `.md` using hugodown output configuration. You must apply the required YAML fields and dual-file editing rules regardless of the authoring format chosen.