Documentation versions

What this documentation describes#

NexusForge Persistence 0.2.0, Unity 6000.6, verified on 2026-09-24. Every page names behaviour that is checked in the repository; where the package and a page disagree, the package wins and the page is a documentation bug — see Support.

One documentation set, one version#

This site documents the current release. It does not yet publish a second version, and it does not pretend to: an "archived 0.1 docs" section would be a maintenance obligation with no readers, and inventing one would be worse than admitting there is one.

How a future version will be added#

The site is generated from a content tree, so adding a version is a content operation rather than a redesign:

content/docs/**.md        the current version, published under /docs/<page>/
content/versions/0.2.md   a note describing a released version, if one is archived

When a breaking release arrives, the intended shape is:

• the new version keeps the clean /docs/... routes, so existing links keep working;
• the previous version's content moves under a version-prefixed tree (/docs/0.2/...) generated from the same Markdown, not hand-copied;
• this page lists the versions that exist, and links to the older set for readers pinned to it.

Version routing exists in the generator today (a page's route is data, not a hard-coded string), so the work at that point is content and a redirect table — not a new documentation system.

Why not version everything from day one#

Because a version selector with one option is noise, and a second set of pages that nobody maintains drifts and then lies. This documentation is honest about what it covers instead.

Next#

• What's new — the release history.
• Changelog — the complete record, including the phases the framework was built in.
• Support — reporting a page that is out of date.