Skip to content
HUBIQ

01

What changed.

Each release, newest first. A site wears a release; this is how its team knows what moving to the next one means.

From CHANGELOG.md, rendered at every build.

02

The HUBIQ design system, by release. A site syncs a release with bash ../hiq-design-v2/sync.sh <version> and records it in design/.hiq-version; syncing the worktree instead records <version>+<commit>, which is fine on a preview and not for a live site. Releases are tagged v<version> on the v2 branch.

Numbering: the major is the system's generation (3 is v2's kit and grounds), the minor a change a site should look at before syncing (a new rule, a changed look), the patch a fix that changes nothing a site has to decide.

3.3.0, 26 October 2026

The base controls and the illustration standard. Look before syncing: one change shows on pages that already exist (the focus ring, below).

  • Controls in the kit (KIT.md, Controls; rulebook 7.35 to 7.40): the secondary button (v2-btn, small and icon-only sizes) and <PillButton>; form fields (v2-form, <Field>, v2-input for text, select and textarea, errors in words with the error icon, never a second colour); checkbox and radio (<Choice>); <Switch>; <Segmented>; <Picks> (filter chips); <Disclosure> (v2-more, a native <details>).
  • <MotionToggle> is in the kit, from the three identical site copies. A site can delete its own (components/MotionToggle.tsx and its .motion-toggle rules) and use the kit's; pass storageKey if the site used another key. Two toggles on one page now keep each other's label in step.
  • <SiteHead> and <SkipLink>: wordmark, up to five links, a phone drawer, in the live hubiq.co.uk header's look. A site with a richer menu (hubiq.co.uk's Initiatives) keeps its own head.
  • <Lost>, the 404 page, for app/not-found.tsx.
  • A focus ring per ground (--focus: ink on light grounds, house green on ink and forest). Anything focusable in a v2 page with no ring of its own now takes it, where it had the browser's default before. Every kit and site rule with its own ring is unchanged.
  • The illustration standard: illustration/README.md (the riso look, the three plates, the brief, the steps, the light-ground reprint) with riso.py, riso_plates.py and light-prints.py moved here from hubiq.co.uk's design-inspo/riso/. Rulebook section 8 points to it.
  • The design system site: a Controls band on /components, a new /illustration page, and the site wears the kit's skip link, motion toggle and lost page.

3.2.1, 26 October 2026

  • tokens.css is values only, so a site imports it as code instead of copying it by hand (starter sites always have; hubiq.co.uk and atomiq.digital from this release). The v1 class rules that sat in it (.card-wash, .lift, a blanket reduced-motion rule) are gone from it; the v1 sites that use them carry their own copies. Nothing a site shows changes.

3.2.0, 26 October 2026

New things for building initiative sites. Nothing changes how an existing page looks.

  • The arrival is in the kit: <Reveal /> and the .arrive, .arrive-group and .rise rules (KIT.md, Arrival). A site that carried its own copy (hubiq-web-v2, atomiq-web) can delete it; the rules are identical, so keeping both changes nothing.
  • A theme template: themes/_template and bash new-theme.sh <name> <Title> [domain]. A new theme starts from HUBIQ's values and passes the checks at once.
  • A starter site: starter/ and bash new-site.sh <name> <Title> <domain>, which makes ../<name>-web, wearing the latest release, built and committed.
  • One folder per session: bash session.sh start|finish <name>. A release now syncs from any folder; a session branch (v2-<name>) can preview unreleased work, with a warning.
  • Each theme's public face: themes/<name>/theme.json (title, summary, where it is worn), read by the design system site. Sites do not sync it.
  • The design system site: site/, for hubiq.co.uk/brand/designsystem (not yet live).

3.1.0, 26 October 2026

The first tagged release. Everything to date, under the version the rulebook already called 3.1-draft.

  • Themes. One system, a look per initiative. themes/hubiq and themes/tenantiq, each a theme.css (every colour and type role) and a THEME.md (its laws and contrast table). A site names its theme in design/.hiq-theme; check-kit.mjs checks the contract and 25 contrast pairings. tokens.css holds no colour.
  • Icon. A shared Icon component and an approved subset of 39 icons.
  • No orphans. Headings wrap balanced and running text wraps pretty in every v2 page.
  • The burst builds from the centre out, on its own trigger (7.34).
  • HUBIQ in capitals, everywhere but the wordmark and the domain (VOCABULARY).
  • Versions. VERSION, this changelog, release tags, and sync.sh <version>.

Before 3.1.0 (untagged)

  • 3.0, 25 September to 19 October 2026. The v2 kit: grounds, the green rule, Inter Tight, the rail, lines, the filling lead, the typed line, strike and replace, statements, the pinned scroll story, named and lit, the second highlight for 5Di, the pill, the lattice, the burst, the fast scroll pace. Synced into every v2 site with a guard against edits in place.
  • 2.0, 8 September 2026. A seven-role type scale with tokens; body leading 1.6.
  • 1.x, August 2026. The first system: tokens, the brand guidelines and the deck template.