Changelog
A reverse-chronological record of everything that has shipped in Orbit — new components, token changes, deprecations, and breaking changes. Entries are added each release cycle.
v0.73.0 — Badge colours fixed
Badges that use a colour such as info, teal, orange or purple showed the brand green after the component token bridge. They now show their own colours again.
- Badge colours — after the component token bridge was added, every Badge with a colour setting drew in the brand green. Info, teal, orange and purple Badges now show the right colours again. Teal maps to scheduled, orange to pending, and purple to discovery.
- Info Button — a Button set to the info colour had the same problem and is fixed. In Storybook it is set with
variant="info". - Package — published as
@open-point-design/orbit-theme0.15.1. Storybook now uses this version.
v0.72.0 — Component tokens built on their own
The component token stylesheet is now generated separately from the Web Awesome theme, and the build checks that component tokens only point at Semantic tokens.
- Component tier on its own — the component tokens (
--orbit-button-*,--orbit-form-control-*and the rest) are now generated into their own stylesheet instead of being produced inside the Web Awesome theme. Any framework can use them, and Web Awesome is no longer needed to get them. The output is identical to before: 1,339 values, unchanged. - Tier rules enforced — the build now stops with a clear message if a component token holds a raw value, points at anything other than a Semantic token, points at a Semantic token that does not exist, or clashes with another token name. This keeps the three tiers (Primitive, Semantic, Component) honest.
- Package — published as
@open-point-design/orbit-theme0.15.0. It also includes the component tokens as a separatecomponents.cssfile, for use without Web Awesome. - Not changed — nothing looks different on the site or in Storybook.
- Changelog — the entries for v0.68.0 to v0.70.0 were rewritten in plain language. How the component tier is generated is in
docs/component-tier-css.md.
v0.68.0 — Component tokens for ten components
Button, form fields, Badge, Checkbox, Radio, Switch, Alert, Modal, Tabs and the shared dropdown menu now ship as framework-neutral CSS variables, with a common size scale, new hover and invalid states, and several contrast fixes.
- Component tokens — Button, Form Control (Input, Select, Textarea, Search), Badge, Checkbox, Radio, Switch, Alert (Callout), Modal and Notification Modal, Tabs and the shared Dropdown and Select menu now have their own
--orbit-*CSS variables. They work in any framework, follow Light and Dark mode and the product theme, and each one points at a Semantic token, never a Primitive. Published as@open-point-design/orbit-theme0.12.0. - One size scale — components share XS to XL sizes, so a button, an input and a select of the same size line up in a row. Modal keeps Small, Medium and Large (480, 640 and 800px) plus Fullscreen.
- New states — fields, Checkbox, Radio and Switch gain Hover and Invalid states. Disabled variants now look disabled; before, several looked identical to the enabled version.
- Modal and Notification Modal — one shared set of tokens. Notification Modal is the Modal’s status variants (Danger, Warning, Success, Info), and a Brand variant is new. The status icon now lines up with the title.
- Switch — track, thumb and label scale together at every size, with proportions closer to the original Web Awesome switch.
- Radio groups — the button style is a single connected control with shared borders and rounded outer corners.
- Dropdown menu — hover and keyboard focus now share one highlight, with a focus ring and a check mark for the selected option, in place of the solid green focus fill.
- Accessibility — the Warning outline, the Dark neutral border and the Dark info text now meet WCAG 2.2 contrast. Placeholder text is darker. The active Tab underline is a darker green (4.59:1 against the page) so the selected state is easy to see. The token check now enforces these ratios for every colour group.
- Documentation — the Alert, Modal, Notification Modal, Tabs and Dropdown pages now match the Figma components, with token references on each component page.
v0.69.0 — Popover and Combobox tokens and documentation
Popover and Combobox now have framework-neutral component tokens and their own documentation pages, and the selected tick in Select, Dropdown and Combobox lists has a token of its own.
- Popover tokens — the floating panel behind help text, filters and pickers now has its own
--orbit-popover-*CSS variables: fill, border, corner radius, padding, the gap to its trigger, arrow size and shadow. They follow Light and Dark mode and each one points at a Semantic token, never a Primitive. - Combobox tokens — a Combobox is a text field that filters a list of options as the user types. It reuses the existing form field and menu tokens, so it matches Input and Select, and adds a few of its own,
--orbit-combobox-*: the maximum list height (320px, then it scrolls), the “No results” message colour, the loading spinner colour, the weight used to highlight matching letters, and the motion for the chevron and list. - Selected tick — the tick on the selected option in Select, Dropdown and Combobox lists now comes from
--orbit-menu-item-selected-icon. It is also fixed in the extra-small and extra-large Select options in Figma, where it was missing. - New documentation pages — Popover and Combobox now exist, with usage guidance, keyboard behaviour, accessibility notes and token references. Both include a React Aria sketch marked as a proposal for Engineering to confirm during the trial. Links to these pages from Tooltip and Search no longer lead nowhere.
- Search — the page now sends “more than one choice” needs to Multi-Select. It previously pointed at Combobox, which only allows one choice.
- Dropdown — the token tables list the selected-tick token.
- Package — published as
@open-point-design/orbit-theme0.13.0. Adds thepopoverandcomboboxgroups, one Semantic size token for the 320px list height, and the matching Primitive.
v0.70.0 — Component tokens now drive Web Awesome
A generated bridge connects the framework-neutral component tokens to the Web Awesome components, so a change to a Button, field or Badge token in Figma now changes the rendered component.
- Component token bridge — Orbit’s component tokens (
--orbit-button-*,--orbit-form-control-*,--orbit-badge-*) are framework-neutral, but Web Awesome only understands its own settings. A new generated stylesheet connects the two, so the Web Awesome components are drawn from the component tokens rather than from separate hand-written styles. Change a token in Figma, export it, and the component changes with nothing edited in between. - What is connected — Button (every variant and appearance, the five sizes, hover, pressed and selected states, the focus ring and the disabled look), Input and Textarea (colours, border, corners, sizes, the filled-outlined and pill options, hover, invalid and disabled), the same field settings for Select and Combobox, and Badge colours. The other Web Awesome components keep their own styling for now.
- Built to stay in step — the bridge reads component tokens only, never Semantic or Primitive ones. If a token it relies on is renamed or removed in Figma, the build now stops with a clear message instead of quietly falling back to Web Awesome’s own look. The generated file is checked on every change.
- Not changed — nothing looks different. The bridge draws the same values the components already used; the difference is where they come from.
- Token sync check — the check that regenerates the theme now also watches the component token file. Before, a change to component tokens alone did not trigger it.
- Package — published as
@open-point-design/orbit-theme0.14.0, with the bridge included intheme.css. How it works and how to extend it is indocs/component-token-bridge.md. - Storybook — a “Component tokens” story that edits tokens live is ready as a draft. Storybook itself needs its theme dependency updated before it picks up this release; its range was stuck on 0.9.x.
v0.71.0 — Orbit documentation available to Claude Code
A read-only Orbit MCP server lets staff search and read the approved Orbit documentation from Claude Code, signed in as themselves.
- Orbit MCP server — staff can now connect Claude Code to Orbit and ask it to search or read the documentation directly. It offers three read-only tools: search the docs, get a page, and list pages. It covers the 88 approved pages (the component, content, data visualisation, get-started and AI tools pages, plus the design spec). The AI knowledge and instruction files are not included.
- Sign-in — people sign in with their own Open Point account through Microsoft. There is no shared password or key. Access is limited to
@openpoint.comaccounts, so guest and external accounts are refused. Each request is logged with the user and the tool used, for audit. - The rest of the site is unchanged — the website still requires a staff sign-in. Only the connection address and its sign-in information are open to the connecting tool.
- Not finished — a real sign-in from Claude Code is still to be tested. It needs a redirect address from Engineering and administrator consent in Microsoft Entra. Rate limiting is not included yet. Setup details and open items are in
docs/mcp-setup.md.
v0.65.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #141 from Open-Point-Design/chore/bump-orbit-theme-0.10.0
- chore: bump orbit-theme to 0.10.0 for the token restructure
- Merge pull request #140 from Open-Point-Design/feat/import-tokens-file
- Import re-exported Components file; drop case-insensitive ref fallback
- Update consumers of renamed and removed token variables
- Import Tokens-file export (lowercase Semantic, dark fixes)
- Add token validator enforcing the three-tier rules
- Merge pull request #139 from Open-Point-Design/main
v0.66.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #142 from Open-Point-Design/feat/import-semantic-scales
- Remove scripts/diff-tokens.js from this branch
- Add motion tokens; map WA transitions and the site onto them
- Import final Tokens/Components exports: code font, 5xl size, text style bindings
- Import Semantic typography/border/focus/scale tokens; rebind Components to Semantic
v0.67.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #145 from Open-Point-Design/feat/import-contrast-fixes
- Import contrast fixes; empty the validator baseline
- Merge pull request #144 from Open-Point-Design/feat/import-shadows-typography
- Merge pull request #143 from Open-Point-Design/feat/token-contrast-check
- Import shadow, curve and text style tokens; move the site onto them
- Add WCAG 2.2 AA contrast check to the token validator
v0.64.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #136 from Open-Point-Design/feat/entra-sso-gate
- fix: only gate the production deployment, not previews
- feat: gate the whole site behind Microsoft Entra ID SSO
v0.60.0
A batch of changes promoted from staging — see the commit list below.
- Convert page shell to
; migrate StatusBadge to wa-badge; fix CardTile slot/layout bugs
v0.61.0
A batch of changes promoted from staging — see the commit list below.
- Rework token pipeline for component-tokens-reference-semantic-directly + dark mode groundwork
v0.62.0
A batch of changes promoted from staging — see the commit list below.
- Update state-token descriptions, fix stale doc references, serve markdown as UTF-8
v0.63.0
A batch of changes promoted from staging — see the commit list below.
- Fix overclaimed Primitive→Semantic→Component chain on the tokens page
v0.59.0
A batch of changes promoted from staging — see the commit list below.
- Remove dark mode toggle; Orbit is light-mode only
v0.58.0
A batch of changes promoted from staging — see the commit list below.
- Correct button hierarchy: Neutral/Accent is the default primary, not Brand/Accent
- Fix leftover dead space in .doc-table (table margin, not just header/border)
v0.54.0
A batch of changes promoted from staging — see the commit list below.
- Rewrite Table docs around the real wa-data-grid component
v0.55.0
A batch of changes promoted from staging — see the commit list below.
- Match wa-data-grid’s pager current-page colour to Orbit’s Pagination
- Improve Table page examples: full-width variants, raised rows, accessible CTA
v0.56.0
A batch of changes promoted from staging — see the commit list below.
- chore: bump orbit-theme to 0.9.19 to unblock publish after this promote
v0.57.0
A batch of changes promoted from staging — see the commit list below.
- Fix doc-table styling and consolidate 4 duplicate copies into global.css
- Remove 3 orphaned components; stop duplicating the build command in vercel.json
v0.50.0
A batch of changes promoted from staging — see the commit list below.
- Sync storybook_story IDs, new WA component registrations, and card/error overrides
- Regenerate component docs — fixes Table’s wa-badge mislabeling
- Convert component-page overview cards to wa-card
- Adopt wa-card for repeated index/landing page tiles
- Add WA accordion/tabs docs, fix widespread aria/table schema bugs, adjust Shiki theme
v0.51.0
A batch of changes promoted from staging — see the commit list below.
- chore: bump orbit-theme to 0.9.15 to unblock publish after this promotion
v0.52.0
A batch of changes promoted from staging — see the commit list below.
- chore: bump orbit-theme to 0.9.16 for split-panel/scroller/page registrations
- Register split-panel, scroller, and page WA components
v0.53.0
A batch of changes promoted from staging — see the commit list below.
- Consolidate WA component registration into a single source of truth
- Upgrade webawesome-pro to 3.12.0, register wa-data-grid
v0.45.0
A batch of changes promoted from staging — see the commit list below.
- fix: accordion background uses surface.raised (#132)
v0.46.0
A batch of changes promoted from staging — see the commit list below.
- chore: bump orbit-theme to 0.9.12 for accordion surface.raised background fix (#133)
v0.47.0
A batch of changes promoted from staging — see the commit list below.
- chore: bump orbit-theme to 0.9.13 for badge colors + invalid field fill fix (#135)
- fix: badge data-color overrides + danger fill on invalid form fields (#134)
v0.48.0
A batch of changes promoted from staging — see the commit list below.
- Merge branch ‘feat/product-brand-colors’ into staging
- Replace custom doc-callout boxes with real wa-callout components
- Fix headings using hardcoded font-weight instead of the heading token
- Replace hero CTA anchors with real wa-button components
- Replace styled anchor/button CTAs with real wa-button components
- Merge branch ‘feat/product-brand-colors’ into staging
- fix: derive link hover/active colors from the real link token
- Merge branch ‘feat/product-brand-colors’ into staging
- fix: split shared border variable into surface vs divider roles
- fix: links use the real color.text.link token, not the brand accent
- fix: round table containers, swap header/body backgrounds to match cards
- fix: round the square component/anatomy/variant preview cards
- chore: remove placeholder AnatomyFigmaEmbed, register remaining WA elements
- fix: swap —orbit-border/—orbit-line-strong, which were mapped backwards
- fix: wire remaining hardcoded border-radius values to —op-radius-* tokens
- docs: add Web Awesome implementation examples for badge, forms, modal, tabs
- Stop forcing Longform serif onto all .prose content
- Replace two remaining hardcoded green literals with real tokens
- Fix search modal rendering left-aligned instead of centered
- Round docs-site chrome to match real WA component radius; remove dotted card texture
- Make docs-site surface/text/border colors follow real Semantic tokens; remove non-brand decoration
- fix: correct Colors.Dark Text.Normal/Disabled contrast bug
- Introduce IBM Plex Mono for the Code token, retire invented display fonts, default to light theme
v0.49.0
A batch of changes promoted from staging — see the commit list below.
- chore: bump orbit-theme to 0.9.14 to unblock publish after this promotion
v0.43.0
A batch of changes promoted from staging — see the commit list below.
- Remove wa-checkbox border-radius override, keep checkmark color fix
- Lowercase the header wordmark to “orbit”
- Add three-axis component status model, Input docs, and Surfaces page
v0.44.0
A batch of changes promoted from staging — see the commit list below.
- Bump orbit-theme to 0.9.11 for checkbox override fix
v0.42.0
A batch of changes promoted from staging — see the commit list below.
- Consolidate semantic radius tokens into role-based scale, move to rounded corners
v0.37.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #126 from Open-Point-Design/feat/component-status-lifecycle-rework
- Rework component status lifecycle to 8-stage model
- Merge pull request #125 from Open-Point-Design/chore/sync-staging-with-main
v0.38.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #127 from Open-Point-Design/fix/component-overrides-css-comment-terminator
- Fix premature CSS comment close in component-overrides.css
v0.39.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #128 from Open-Point-Design/fix/bump-orbit-theme-version-for-comment-fix
- Bump orbit-theme to 0.9.8 to actually publish the CSS fix
v0.40.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #129 from Open-Point-Design/fix/sync-tokens-swallowed-publish-failure
- Stop sync-tokens.yml swallowing real publish failures via workflow_call
v0.41.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #130 from Open-Point-Design/fix/theme-relevance-check-for-publish-gate
- Gate the orbit-theme publish-conflict failure on an actual theme-relevant diff
v0.36.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #124 from Open-Point-Design/fix/heading-font-weight-token-alignment
- Bump orbit-theme to 0.9.7
- Align Heading font-weight token to its real 500 value
- Merge pull request #123 from Open-Point-Design/chore/sync-staging-with-main
v0.34.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #120 from Open-Point-Design/feat/orbit-font-tokens-and-npm-loading
- Make font-family theme-able and load fonts in the npm package
v0.35.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #122 from Open-Point-Design/fix/noto-fallback-font-loading
- Load Noto Sans/Noto Serif alongside their primary typefaces
- Merge pull request #121 from Open-Point-Design/chore/sync-staging-with-main
v0.26.0 — Contrast fixes, Pending/Scheduled colours, brand-tinted neutral button
Fixes two real accessibility contrast regressions in Neutral and Success status tokens, adds Pending and Scheduled as real status colours, restores bold/semibold body text styles, and gives the default neutral button a brand-tinted background.
- Accessibility fix —
status.neutral.fill.loudand the generalneutral.fill.loudwere resolving through an accidental alias into the Brand collection instead of a real neutral tone; both now resolve toneutral.40, restoring WCAG AA contrast (previously as low as 3.22:1) - Accessibility fix —
status.success.on.quietdarkened to restore AA contrast after an earlier refinement darkened its background (was failing at 4.30:1, now 5.54:1) - Status colours —
status.info’s fill/border/text values refined, and Pending (orange) and Scheduled (teal) promoted from an interim decorative group to real status colours, verified against contrast minimums - Typography — restored the four bold Body text styles dropped in an earlier export, added new Semibold variants, and added
'Noto Sans'/'Noto Serif'as the multi-lingual fallback in the body/heading font stacks - Button —
wa-button[variant="neutral"][appearance="accent"](the default button) now uses the product’s brand-05 tone as its fill instead of true neutral, giving it a deliberately dark, brand-tinted background distinct from status components brand.fill.quietrestored as a distinct value frombrand.fill.normal
v0.27.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #111 from Open-Point-Design/chore/test-promote-workflow-fix
- Bump orbit-theme to 0.9.3 to test the new promote-workflow wiring
- Merge pull request #110 from Open-Point-Design/chore/promote-workflow-no-pat
- Drop TODO placeholder text from the no-AI changelog fallback
- Remove promote-to-production’s dependency on PROMOTE_PAT
v0.28.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #113 from Open-Point-Design/chore/test-is-main-fix
- Bump orbit-theme to 0.9.4 to test the is_main fix end to end
- Merge pull request #112 from Open-Point-Design/fix/promote-workflow-is-main-flag
- Fix: sync job skipped Storybook redeploy/npm publish when promote was dispatched from a non-main ref
v0.29.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #114 from Open-Point-Design/fix/typography-page-crash-and-decisions
- Fix production-breaking crash on /foundations/typography, document real typeface decisions
v0.30.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #115 from Open-Point-Design/fix/typography-claim-hover-and-feedback-widget
- Fix real Tally feedback submission, remove unverified claim, fix hover contrast on typography page
v0.31.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #116 from Open-Point-Design/fix/tokens-page-benefit-card-styling
- Update spacing and radius page status to in-review
- Update colour page status to in-review
- Update tokens page status to in-review
- Restyle “Why tokens?” cards on the tokens page to match Principles
v0.32.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #117 from Open-Point-Design/feat/feedback-widget-modal-and-branding
- Centre the Tally popup, set expectations on click, brand the feedback widget as an Orbit card
v0.33.0
A batch of changes promoted from staging — see the commit list below.
- Merge pull request #119 from Open-Point-Design/chore/sync-staging-with-main
- Merge pull request #118 from Open-Point-Design/feat/feedback-widget-modal-and-branding
- Remove card styling from page feedback widget; sync regenerated tokens/docs
v0.24.0 — Form controls and tooltips now reflect real tokens
Form control and tooltip colours are now sourced from the Styles token collection instead of disconnected hand-authored values, fixing Storybook forms and tooltips that never reflected token updates.
- Form controls & tooltips — background, border, label, placeholder, and content colours are now generated directly from Figma’s Styles collection instead of hardcoded overrides that silently shadowed real token values
- Build hygiene — the published theme package’s build output is no longer committed to git, since it was permanently out of sync with what’s actually published and caused real confusion when debugging
v0.25.0 — Checkbox checkmark matches its success-green fill
The checkbox checkmark icon now uses the success colour family to match its fill, instead of defaulting to brand.
- Checkbox — the checkmark icon colour now follows the success colour family (matching the checked-state fill), rather than defaulting to WA’s built-in brand assumption
v0.23.0 — Semantic tokens now drive the live theme
Reconnects the Semantic token layer to the actual Web Awesome theme output, so colour and corner-radius decisions made in Figma now genuinely reach the live site instead of a disconnected snapshot.
- Token pipeline —
generate-wa-theme.jsnow reads the current Semantic and Colors.Light token files directly instead of a frozen snapshot, so colour and corner-radius updates in Figma reach the live theme automatically - Corner radius — inputs, cards, and tooltips now render with their actual intended radius (previously a global density override left every Web Awesome component square regardless of what the tokens said)
- New
tokens.json— a single merged file combining every token collection is now generated for engineers and AI tooling to read
v0.22.0 — Status colour accuracy & unified tokens page
Corrects status and brand colour token values to match the refined Web Awesome palette, renames the warning/danger status groups for consistency, and merges the primitive and semantic token pages into one filterable table.
- Colour tokens — Corrected status colour values (neutral, info, success, warning, danger) and the brand text colour to match the refined Web Awesome component palette, including making the neutral status colour intentionally brand-tinted. Renamed the “caution” and “error” status groups to “warning” and “danger” for consistency with Figma.
- Foundations — Merged the separate primitive and semantic token pages into a single filterable “All tokens” table.
v0.20.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #83 from Open-Point-Design/chore/brand-collection-token-migration
- chore: source brand/component tokens from Figma’s new Brand collection
v0.21.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #84 from Open-Point-Design/chore/semantic-brand-reconciliation-and-inverse-tokens
- chore: reconcile semantic/component brand tokens, add missing text/surface roles
v0.19.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #78 from Open-Point-Design/fix/foundations-colour-page
- fix: renumber docs-site chrome pipeline (—op-color-*) to WA convention
- Merge pull request #77 from Open-Point-Design/feat/secondary-component-group
- feat: build Secondary as a proper component token group
- Merge pull request #76 from Open-Point-Design/fix/component-border-quiet
- fix: add border-quiet component token, confirmed against Figma Theme (Colors)
- Merge pull request #75 from Open-Point-Design/feat/wa-native-component-tokens
- Merge remote-tracking branch ‘origin/staging’ into feat/wa-native-component-tokens
- feat: WA-native component token layer, renumber primitives to WA convention
- Merge pull request #73 from Open-Point-Design/update/foundations-design-tokens
- DES-527 Updated the primitive colors, font family, and SP/OP toggle in foundations page
- DES-527: Orbit Site Foundations documentation - Update Colour, Typography, Spacing, and Radius pages
- chore: regenerate llms.txt after rebase onto staging
- fix: avoid literal
- DES-482: Publish ORBIT token foundation pages (Colour, Spacing, Radius, Elevation, Motion)
v0.17.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #70 from Open-Point-Design/update/get-started-restructure
- Merge branch ‘staging’ into update/get-started-restructure
- Revert “Merge pull request #71 from Open-Point-Design/feat/orbit-ux-improvements”
- Merge pull request #71 from Open-Point-Design/feat/orbit-ux-improvements
- DES-543: Orbit site UX improvements — light default, view transitions, snappier animations, collapsible sidebar
- DES-542: Restructure Get Started — consolidate pages and split nav into sections
v0.18.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #74 from Open-Point-Design/revert/des-542-get-started-restructure
- Remove Amy’s test page
- Revert “Merge pull request #70 from Open-Point-Design/update/get-started-restructure”
v0.15.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #66 from Open-Point-Design/chore/add-favicon
- Add Orbit favicon
v0.16.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #69 from Open-Point-Design/chore/ai-layer-callout-and-llms-links
- AI Layer: accessible callout, restore design team’s AI statement
- llms.txt: use repo-relative links, regenerate on every deploy
- Merge pull request #68 from Open-Point-Design/chore/simplify-promote-workflow
- Simplify promote-to-production: push straight to main, no PR
v0.14.0 — [TODO: describe this release]
TODO: write a one-sentence summary — drafted without AI, ANTHROPIC_API_KEY was not set.
- Merge pull request #64 from Open-Point-Design/fix/homepage-redirect-loop
- fix: serve homepage at /get-started/overview to avoid redirect loop
- Merge pull request #63 from Open-Point-Design/feat/launch-prep-ia-and-ai-layer
- feat: launch-prep IA restructure + repo-first AI layer
v0.10.0 — Fully automated release promotion
The promote-to-production pipeline no longer needs manual intervention to draft a release branch — a human just clicks a link to open the final PR.
- Automated release branch — the promote-to-production pipeline previously tried to push the drafted changelog straight to staging, which staging’s branch protection silently rejected for the automation’s own account (unlike a real admin). It now drafts the release on a fresh branch instead, which sidesteps the restriction entirely
- One-click promote PR — this org’s enterprise policy blocks automation from opening pull requests outright, so the pipeline now prints a ready-to-go link in the workflow summary instead of trying (and failing) to open the PR itself
v0.11.0 — Release pipeline hardening
Two more bugs fixed in the release pipeline itself, plus corrected references to the retired token build process.
- Changelog version numbering fixed — the auto-drafted changelog picked its “latest” entry by sorting filenames as text, which broke once a minor version reached double digits (
v0-10-0sorted beforev0-9-0) and silently reused an already-taken version number. Now compares versions numerically - Package changes now trigger a republish — the “Sync design tokens” action only watched the raw token JSON files, so changes to
component-overrides.css, the theme generator, or thewa-themepackage itself wouldn’t republish@open-point-design/wa-themewithout a manual trigger. Broadened to cover all of it - Documentation corrections — fixed stale references to the retired
build-tokens.jspipeline inCLAUDE.mdand the AI-context spec file
v0.12.0 — Migrated to Web Awesome Pro
Orbit and Storybook now run on the licensed Web Awesome Pro package instead of the free tier.
- Web Awesome Pro — replaced the free
@awesome.me/webawesomepackage with the licensed@web.awesome.me/webawesome-propackage across the site and the shared theme package. Same components, same colours (our own token-driven theme is still the source of truth) — just running on the Pro registry now, which unlocks access to Pro-only components going forward
v0.13.0 — Fixed a changelog version collision
The release pipeline no longer reuses a version number that was already published, closing a gap that surfaced during today's Web Awesome Pro release.
- Changelog version drift fixed — the release pipeline computed the next version from staging’s changelog history, which can lag main’s since changelog entries only ever land on main directly. This caused a real version-number collision during today’s release, caught in review before it shipped. Now checks both branches’ history before picking the next version
v0.8.0 — Packaged Web Awesome theme, AI Layer policy update
The Web Awesome theme is now a published package consumable by any project, plus a values-led AI usage policy on the AI Layer page and two CI reliability fixes.
- Packaged Web Awesome theme — the theme CSS and Web Awesome component registrations are now published as
@open-point-design/wa-themeto GitHub Packages, generated and published straight from this repo’s CI. Orbit-storybook now installs it as a dependency instead of fetching raw files and hand-wiring ~27 individual component imports; the same package is available for future Open Point and Social Point product apps - Human-led, AI-assisted policy — replaced the “Responsible use” section on the AI Layer page with a values-led statement: the Product Design team has final say and is involved start to finish, AI never ships as raw output. Broadened the audience framing beyond government to multiple sectors and, via Social Point, citizens and communities
- CI reliability fixes — token sync now runs on staging only (main is push-restricted), and the Storybook redeploy hook fires on main instead, matching how the promote-to-production flow actually moves changes
v0.9.0 — Resilient changelog drafting
The release pipeline no longer blocks on a missing Anthropic API key — it drafts a plain placeholder changelog entry instead.
- Resilient changelog drafting — the promote-to-production pipeline previously hard-failed when
ANTHROPIC_API_KEYwasn’t configured, silently blocking releases. It now falls back to a plain, un-worded changelog entry (one bullet per commit) instead, which a human still reviews and edits before the release PR merges
v0.7.0 — Guidelines & Patterns sections, tool-agnostic AI docs
A new top-level Guidelines section, a scaffolded Patterns library, tool-agnostic AI documentation, and launch URL and reference fixes.
- Guidelines section — new top-level Guidelines section (Accessibility, UX Guidelines, Content & Writing) with a
/guidelineslanding, moved out of Foundations so Foundations is now purely visual (tokens, colour, typography, spacing, radius) - UX Guidelines — new page covering the layer above component selection: composition and flow, state completeness, page-level accessibility, content and tone, suite-first consistency, escalation triggers, and a pre-ship review rubric
- Patterns — scaffolded the Patterns section: a
/patternslanding plus four proposed pattern pages (forms and multi-step flows, empty states, destructive-action confirmation, notifications and feedback), built on a new PatternPage layout with reusable Usage / DoDont components - Tool-agnostic AI docs — reframed the AI Layer so Orbit’s context reads as portable across any AI tool, with Claude as the team’s primary example rather than the layer itself
- Contributing — Editing docs now points to the Confluence guide “Contributing to Orbit with Claude Code” as the single source of truth for making changes
- Navigation — reordered the top-level nav (Data Visualisation now last) and made the AI Layer nav item navigable
- The Designers — new
/get-started/the-designerspage introducing the design team - Launch fixes — corrected stale references (repository → Open-Point-Design/orbit, canonical URL → orbit.openpoint.com) and regenerated
llms.txt
v0.6.0 — Web Awesome theme pipeline and Alert component
Orbit is now the single source of truth for the Web Awesome theme shared with Storybook, every component used in docs actually renders natively, and a new Alert component ships with a nav and foundations refresh.
- Web Awesome theme pipeline — orbit now generates the shared Web Awesome theme (
wa-theme.generated.css+component-overrides.css) from its own design tokens; orbit-storybook fetches this output instead of re-deriving it, removing a second hand-maintained copy that had drifted out of sync - Native component rendering — registered every Web Awesome custom element actually used in component docs (button, tooltip, spinner, tag, avatar, badge, input, textarea, option, progress bar, details, checkbox, select, divider). Previously only
wa-iconandwa-calloutwere registered, so these silently never upgraded into real components - Social Point theming fix — the brand toggle now correctly switches Web Awesome components to Social Point colours, not just the site’s own chrome
- Alert component — added a new Alert page with
wa-callouttheming and a single-column variant layout - doc-callout component — replaced bespoke callout styles across the site with a shared, dark/light-mode-aware
doc-calloutcomponent - Nav and foundations refresh — UI improvements across navigation, foundations pages, and component knowledge docs
- Design token updates — applied the latest Figma token export (focus, border-subtle, text-subtle, and other semantic values)
v0.5.0 — Contribution workflow and accessibility fixes
Release automation, a PR template, accessibility improvements to the changelog page, and a dedicated staging environment for team review.
- Contribution workflow — Added a PR template with JIRA ticket field, changelog template, and a Promote to production GitHub Actions workflow to manage releases from staging to main
- Staging environment — Renamed preview branch to staging; configured
orbit-ds-staging.vercel.appas the stable staging URL for team review - Changelog accessibility — Improved the changelog page: affected page tags now use correct semantic markup (nav, list), link contrast lifted from 1.6:1 to 15:1, pill backgrounds made visually distinct, and type tags removed in favour of version number and date
v0.2.0 — Core Component Documentation
Fully documented Button, Input, and Alert components — all six tabs each, including Open Point and Social Point migration guidance.
- Button — complete six-tab documentation: Overview (all variants and states), Style (token table), Code (React + HTML examples, keyboard behaviour), Accessibility (ARIA patterns, focus management), Open Point migration, Social Point migration
- Input — complete six-tab documentation: all input states including error with
aria-invalid+aria-describedbypattern, helper text, token table, React and HTML code examples - Alert — complete six-tab documentation: four variants (informational, success, warning, error), toast pattern with live region guidance, focus management on dynamic alerts
- Fixed full-width layout on overview page
v0.3.0 — Data Visualisation and Content & Writing
Two new fully-written sections — Data Visualisation and Content & Writing — plus fully authored content for all five chart type pages.
- Data Visualisation — overview with guiding principles and chart selection guidance; Colour in charts with WCAG 1.4.11 requirements, colour-blindness guidance, and token reference tables; fully authored pages for Bar chart, Line chart, Area chart, Pie and donut, Scatter plot, Maps, and Accessibility in data visualisation
- Content & Writing — overview; Voice & tone (four attributes with before/after examples); UI text section (Action labels, Empty states, Error messages, Form labels, Notifications, Confirmation dialogs); Formatting section (Capitalisation, Numbers & dates, Punctuation); Inclusive language; Writing for accessibility
- 45 component stubs upgraded with real descriptions across all Buttons, Forms, and top-level component categories
v0.4.0 — Search, Accessibility Audit, and CMS
Site-wide search powered by Pagefind, targeted accessibility fixes across the site, and a working Decap CMS with GitHub OAuth.
- Search — Pagefind integration indexing all 94 pages; search modal (Cmd+K / Ctrl+K) with keyboard navigation, accessible focus management, and highlighted excerpts; search trigger button in site header
- Accessibility fixes — skip link updated to
:focus-visible; contrast failures resolved on nav section labels, nav group labels, component page metadata, RoadmapCTA metadata, and search modal text (all werecolor-text-mutedat 2.80:1 on warm white, nowcolor-text-secondaryat ~7.25:1) - Decap CMS — GitHub OAuth proxy deployed as Vercel serverless functions; Changelog collection wired to
src/content/changelog/so new entries can be created and edited without touching code - Component page meta (status badge, last updated) excluded from search index to prevent excerpt noise
v0.1.0 — Promptathon Build
Initial release of Orbit — scaffolding, token system, foundations, and Get Started documentation.
- Complete Astro repo scaffold with Vercel deployment configuration and Figma sync script
- Full colour token system: 8 ramps (Green, Teal, Blue, Purple, Red, Orange, Yellow, Neutral) × 9 steps (50–900) with semantic alias tokens
- Colour foundations page with swatch grid, contrast ratios, semantic alias table, accessibility callouts, and click-to-copy on all token names and hex values
- Get Started section: Overview, Principles, For designers, For developers, Using Orbit with AI, How to contribute, Component lifecycle, Contribution lifecycle, Changelog, Roadmap, Glossary
- Shared components: StatusBadge, AccessibilityCallout (Why/How/Watch variants), RoadmapCTA, PageFeedback, ColourSwatch with click-to-copy
- Six-tab ComponentPage layout with full keyboard navigation (arrow keys, Home/End)
- Foundation stubs: Typography (type specimens), Spacing (visual scale), Accessibility, Web Components (Web Awesome token mapping)
- Components index page with 47 component stubs across Buttons, Forms, and top-level categories
- Decap CMS configuration with collections for Get Started, Foundations, Components (all six tabs), Patterns, Guidelines, and Changelog
- Accessibility-first site: skip navigation, semantic HTML, keyboard focus indicators, prefers-reduced-motion support