hugo-blog

What problem does it solve?

Ensures consistent, error-free publishing of Hugo blog posts by enforcing a reliable two-file workflow, strict front matter conventions, and a repeatable pre-push process.

Core Features & Use Cases

• Two-file source-of-truth workflow: author in content/posts/*.rmd, render to content/posts/*.md, and never edit generated output directly.
• Strict file naming and series management: create series posts as {series_name}_part_{NN}.rmd with zero-padded numbering, starting new series at _part_01.
• Front matter validation for Hugo/hugodown: apply required YAML fields (including output: hugodown::md_document), correct slug/date formatting, and appropriate alias/summary metadata.
• Release readiness guardrails: require updating readme.md post counts before pushing to main, ensuring the repo stays in sync with published content.

Quick Start

Run the md-format step on your post’s source .rmd, render it to .md using the provided R command, update the root README series table/counts, then commit both the .rmd and rendered .md and push to main for Netlify deployment.