How this content pipeline works

Every file in `src/content/blog` is an article. Add a file, get a page, a sitemap entry and structured data — no code change. ## What is derived rather than declared Reading time is computed from the body, because a hand-typed number goes stale the first time anyone edits a paragraph. The topic is checked against a closed list, so a typo is a fallback rather than a fourth pill nobody notices. ## What to know before you rely on it Every file here is **live the moment it is committed**. There is no date filtering, and the site is statically built, so a future-dated post does not appear on its date — nothing triggers a rebuild. If you want a publishing queue, keep drafts in a separate directory and move them across deliberately.