Each post uses the packaging repository metadata contract. Set metadata_version to the current packaging schema version. This value can use a different version from the HTTP app.
- Set a numeric
schemafield on every post. - Provide every required value. Do not infer missing values.
- Reject the legacy
meta_versionfield. - Reject unknown fields to keep the public contract stable.
- Follow the packaging repository metadata migration rules when the schema changes.
Store one JSON post in the shared content directory at content/blogs/.
{
"metadata_version": "<packaging metadata schema version>",
"schema": 2,
"slug": "rolling-releases",
"title": "Following rolling releases",
"summary": "How to follow Node.js rolling builds.",
"published_at": "2026-08-18T12:00:00Z",
"updated_at": "2026-08-18T12:00:00Z",
"author": "Eliware",
"tags": ["releases", "rolling"],
"content_format": "markdown",
"created_at": "2026-08-18T11:00:00Z",
"category": "releases",
"last_verified_at": "2026-08-18T12:00:00Z",
"tested_on": ["Repository content review"],
"status": "published",
"content": "# Rolling releases\n\nMarkdown content goes here."
}Follow these field rules:
- Use unique slugs with lowercase letters, numbers, and hyphens.
- Set
title,summary,author, andcontentto non-empty strings. - Set
content_formattomarkdown. - Set
created_atno later thanpublished_at. - Set
categoryto a documented editorial category. - Set
last_verified_atto the date when a writer checked technical claims. - List each platform used to check technical claims in
tested_on. - Set optional
hero_imagepaths under/assets/. - Set optional
related_slugsvalues to valid post slugs. - Set optional
seriesand positiveseries_ordervalues for tutorial series. - Use UTC ISO 8601 timestamps ending in
Zforpublished_atandupdated_at. - Set
updated_atno earlier thanpublished_at. - Set
tagsto a non-empty array of unique strings. - Set
statustodraftorpublished. Drafts do not appear on public pages or RSS. - Derive canonical URLs from
slug. Do not store URLs in the post.
The schema checker lives at src/backend/blog/schema.mjs. The matching test lives at tests/backend/blog/schema.test.mjs. The HTTP loader, API, post pages, and RSS use the same store validation.
Set BLOG_DIR to a content checkout, then run npm run check:blogs. The command checks each JSON post and finds duplicate slugs before publication.
/bloglists published posts./blog/category/<category>filters posts by editorial category./blog/<slug>returns one post page./blogs/redirects to/blogfor path compatibility./termsand/tosreturn the Terms page./api/v1/blogsreturns the published post collection./api/v1/blogs/<slug>returns one post and safe rendered HTML./feed.xmlreturns RSS 2.0 XML.
The HTTP image contains the post viewer and schema code. At runtime, it reads JSON posts from the shared content volume. A writer can add or edit a post without rebuilding the image. Drafts stay out of public pages, APIs, RSS, and the sitemap.