Documentation versions
How versions work
Section titled “How versions work”The header switcher lists major lines and main, never every minor tag.
Each selection is a separate documentation tree:
| Switcher label | URL | Meaning |
|---|---|---|
| 0.x | /0.x/ |
Docs frozen at the latest 0.x release (today v0.4.1) — latest (default) |
| main | /main/ |
Unreleased tip from the main branch (opt-in) |
| 1.x (later) | /1.x/ |
Docs for the 1.x package line, once that major ships |
The site root (https://orbit.almasix.com/) sends you to 0.x. Latest is always the newest major. main is never the default. Minor releases land in Release notes, not as extra switcher rows.
astro dev on a checkout shows the main tree unprefixed (http://localhost:4321/) so you can edit pages without building both trees.
Not on latest
Section titled “Not on latest”If you open a line that is not the latest major — including main — a banner appears with a link back to the latest documentation.
| Package | Docs switcher |
|---|---|
almasix-orbit==0.* |
0.x (latest) |
Working from unreleased main |
main |
almasix-orbit==1.* (later) |
1.x |
Match the switcher to the package you have installed. APIs on main can move before the next tagged release; stay on 0.x when you are following a published version.
What “0.x” contains
Section titled “What “0.x” contains”The /0.x/ tree is built from the newest stable v0.* git tag — the same docs that shipped with that release. Pages added on main after v0.4.1 are not on 0.x until the next 0.x release.
When a new 0.x tag is published, the next docs deploy rebuilds /0.x/ from that tag automatically. The build fetches tags first, so /0.x/ tracks v0.4.1 (and later 0.x tags) rather than whatever main happens to contain.
What to read first
Section titled “What to read first”New to Orbit? Start at Installation and Quick start, then the Features checklist. Package import map: Packages.