A blog template looks fine with one post and falls apart with fifty: the archive page overflows, the excerpt truncates mid-word, the tag cloud has one enormous entry. This produces complete posts, frontmatter included, so you can fill a site and see what breaks.
What you can control
- YAML frontmatter with title, slug, date, author, tags and a draft flag — the fields most static site generators expect.
- Section count is yours to set, so you can produce both a 200-word note and a long read.
- Optional pull quotes and code blocks exercise the two elements that most often break a prose stylesheet.
- Three topic vocabularies so the posts do not all read identically.
What this is not
The prose is assembled from word lists, so it reads as filler on close inspection. It is built to fill a layout and a search index, not to be read.
Questions
Can I import these straight into a static site generator?
Yes. The frontmatter uses the conventional keys for Hugo, Astro, Eleventy and Jekyll. Save each post as its own .md file in your content directory.
Are the slugs unique?
They derive from the title, so a repeated title produces a repeated slug. For a large batch, append the row index or generate with a different seed.
Why include a draft flag?
Because roughly a quarter of the posts come out as drafts, which is how you find out whether your build actually filters them.