Glossary & Learning Atlas
Orbit keeps one body of plain-language teaching material and publishes it in two places: inside the app, and here on the website. The website copy needs no install and no account.
Read it here
Section titled “Read it here”- Glossary — every published term, A–Z, with search and category filters. Each term has its own page: the short definition, the longer explanation, when you would use it, related terms, and the learning paths that teach it.
- Learning Atlas — guided reading orders through the glossary. Each path is a short sequence of terms with the reason each one comes next, and every step links back to the full term page.
The same content inside Orbit
Section titled “The same content inside Orbit”The titlebar book icon (Ctrl/Cmd+?) opens the in-app reading list: the same categorized terms with search, an A–Z rail, pin/recent/need-review states, and term detail pages. The Learning Atlas map view shows the same paths in a collapsible sidebar. Community term suggestions mirror to Discord.
The in-app surface adds reading state — what you pinned, what you read recently, what you flagged for review. The website surface is stateless and linkable, which makes it the one to send to someone else.
How the published content is produced
Section titled “How the published content is produced”Both website surfaces are built from two deterministic JSON exports generated from the source material by
npm run docs:data:build at the repository root. The website imports nothing from the Orbit dashboard, Electron, or
any runtime module — it is static data and static pages.
Not everything in the source is published. Two kinds of entries are held back:
- Internal implementation vocabulary — names for Orbit’s internal contracts that describe how the app is built rather than anything you would do with it. These are removed from the exported data, not merely hidden at render time.
- Content pending editorial freshness review — entries that assert a current product or model standing that cannot be re-verified at build time. A wrong claim on a teaching page is worse than a stated gap.
Every source entry and every source path is either published or counted under one of those reasons. The counts are shown at the bottom of the Glossary and Learning Atlas pages, so a gap is always visible rather than silent.