Skip to main content

April 17, 2026 — Per-release documentation format

NeoSpace
Product

This update moves customer-facing release notes out of the documentation tree and into the blog plugin, so /docs stays focused on reference material while chronological updates live under /release-notes, similar to how many product teams publish changelogs (for example PostHog and Datadog).

What's new​

  • Blog-based releases — Each delivery is a dated folder in blog/ with index.md, its own URL, and RSS/Atom feed support.
  • Clear separation — Documentation remains the long-lived product reference; Release notes are the timeline of what shipped.

Improvements​

  • Room for screenshots under static/img/release-notes/ when a release is best explained visually.
  • Authoring script — npm run release-notes:new -- YYYY-MM-DD short-slug scaffolds a new post (see scripts/new-release.mjs).

Notes for administrators​

  • No change is required to SSO, API keys, or tenant configuration for this documentation-only update.
  • If your organization mirrors the site, update bookmarks from /docs/release-notes/... to /release-notes/... (post slugs are listed on the release notes index).

Next releases​

Future NeoSpace platform deliveries (NeoData, connectors, training, inference, and so on) follow the same pattern: add a new folder under blog/ with index.md, tag with release, and publish with the site build.