Writing blog articles

Setup and configuration

Blog content is stored in src/resources/content.ts and blog-posts.ts. This is repository-managed content; there is no CMS publishing service. Each Post needs a unique slug, title, description, category, date, related guide, and sections.

{
  slug: 'your-article',
  title: 'A specific reader question',
  category: 'Guides',
  date: '2026-09-07',
  guide: 'web/local-setup',
  sections: [{ id: 'start', title: 'Start here', paragraphs: ['Your original text.'] }]
}

Implementation workflow

Follow a complete existing Post object for the remaining type fields. Keep the slug stable after publication so shared URLs continue to work. Headings need unique section IDs for the table of contents and anchor links.

Categories derive from the article catalogue. The index uses URL-based filtering, and article routes generate metadata from the content. The guide value must match an existing documentation slug; related content should lead to a useful next step.

Verification and troubleshooting

Run the content tests, open the article route, follow its related guide, and check the filtered index. Check dates and claims against the source material. Do not publish placeholder links or claim that an integration has been verified merely because it appears in an article.