Brand
Changelog v1.4
Home / Resources · Roadmap

Roadmap

A living plan for how the Snyder Design System aligns design tooling with code.

LIVING DOC
Updated May 12 2026 · v1.4.4
BrandOS v1.4
Shipped
In flight
Planned
Exploring

01 · Shipped

What’s in production

Every release from v1.2 onward — each section links to the files that carry the work.

v1.4.4 May 12 2026

Liquid + Alexander Labs profiles, premium Gotham, brand count = 5

  • Liquid Intelligence & Marketing brand profile added — single design system covering both sub-brands.
  • Alexander Labs brand profile added — applied-research identity on teal + lime in Electrolize + Poppins.
  • Alexander tokens promoted from megazord overlay into @brandos/tokens proper — no more public-folder overlays.
  • Premium Gotham fonts self-hosted via `pnpm setup-fonts` — script mirrors megazord pattern, downloads OTFs from liquidint.com into gitignored public/fonts/Gotham/.
  • Brand profiles support optional logoSvgDark — dark-mode mark swap honoured at [data-theme="dark"].
  • Brand count derived dynamically from brandProfiles.length — gallery + typography sample stay accurate as tenants land.
  • New brandOS/docs/Brand/AddingABrand.md — canonical agent prompt + yaml input checklist for landing future brand profiles end-to-end.
  • llms.txt + llms-full.txt refreshed; @brandos/ui/assets README rewritten; public/assets CDN-staging README added.
v1.4.3 May 12 2026

Editorial brand profile pages

  • /brands index rebuilt as editorial gallery — stats strip with live pulse, 3-up brand cards with mark + 19-stop palette + typography preview, contract callout with terminal-style code snippets.
  • /brands/[slug] pages match the colors page editorial pattern — brand-tinted hero, one section per palette with click-to-copy 19-stop swatch strips, hex populated via canvas OKLCH → sRGB.
  • Semantic slots rendered as rich visual cards — colored splash, usage hint, token/class key-value rows.
  • Typography specimens render in each brand's actual font (loaded on-demand from Google Fonts) with Aa display, pangram, character set, and size ladder (H1/H2/H3 + Lede/Body/Caption).
  • Primitive check switched to a live app mockup (console with stats, search, progress, actions) that flips entirely on data-theme — light + dark side-by-side, brand favicon in the header.
  • Previous/next brand navigation at the bottom of every detail page.
  • SideNav Brand Profiles entry expands into ControlBus / MCIT / Micro Innovation just like Components.
  • BaseLayout exposes a head slot so any page can inject extra <link> / <meta> tags without forking the layout.
v1.4.2 May 12 2026

Canonical SVG assets in @brandos/ui

  • All brand logos, marks, login backgrounds, and shapes consolidated into @brandos/ui/assets.
  • 34 generic icons moved out of brand/public into @brandos/ui/assets/icons (auto-discovered via glob).
  • New <Icon name="…"> Astro component inlines SVG content — preserves currentColor and CSS theming over opaque <img>.
  • Brand profile marks render inline via brandFaviconsRaw so tenant colours inherit page theming.
  • Liquid shapes renamed from shape-01/02 + bg-01/02 to semantic names (flow-composition, side-arcs, slide-rays, slide-base).
v1.4.1 Apr 24 2026

Discoverability, search, mobile polish

  • Cmd-K search palette — fuzzy title + section match across brandNav.
  • Per-page SEO meta, OG card, sitemap.xml, robots.txt.
  • Global focus-ring audit via shared stylesheet.
  • Mobile drawer close button + tile/footer/home responsive fixes.
  • Raw-CSS-to-Tailwind sweep across every page stylesheet.
v1.4 Apr 22 2026

BrandOS editorial site

  • Dropbox-style home shell — sticky header, tile grid, footer.
  • Editorial inner pages across Foundations, Expression, Practice.
  • Click-to-copy swatches, icons, type tokens, and prompt fragments.
  • AI Guardrails v2 with allowed / forbidden / reuse-ladder matrix.
v1.3 Mar 18 2026

Hackerman theme

  • Second brand ships as a theme, not a fork — tokens flip on data-brand.
  • Light + dark mode parity verified across semantic slots.
  • Graygreen neutral scale added to the token package.
v1.2 Feb 04 2026

Fluid type + motion tokens

  • clamp()-based fluid type scale (xs → 9xl) replaces static sizes.
  • Five easing curves + five durations exposed as --brandOS-ease-* / -duration-*.
  • prefers-reduced-motion wired through every component.

02 · Near term

What’s next

Planned and in-flight work for Q2 – Q3 2026. Dates are intent, not commitments.

Q2 2026 in flight

Semantic token consolidation

Collapse the light/dark token pairs into a single light-dark() slot per semantic role.

tokenssemantic
Q2 2026 in flight

Figma variable alignment

Match Figma variable names to documented token names so handoff stops translating.

figmahandoff
Q3 2026 planned

Logo + font PNG/TTF bundles

Generate PNG rasters + packaged .ttf downloads so Downloads page ships beyond SVG.

downloadsbuild
Q3 2026 planned

Icon set .zip bundle

CI step that zips @brandos/ui/assets/icons/*.svg into /downloads/snyder-icons.zip on each release.

downloadsbuild
Q3 2026 in flight

Cross-app SVG asset consolidation

Migrate megazord, interOS/supervisor, and apps/global/* off local vector-graphics/ folders onto @brandos/ui/assets.

consolidationcross-product
Q3 2026 planned

Storybook + visual regression

Per-story axe run + Chromatic visual diff in CI. One story per shipped component.

qualityci
Q3 2026 planned

Migration guides

Recipe-style guides for token renames and deprecated components.

docsmigration
Q4 2026 planned

Per-component Storybook coverage

Every shipped brandOS/ui web component gets one story with axe + visual snapshot coverage.

qualitystorybook

03 · Longer term

On the horizon

Exploration candidates that depend on upstream decisions or org readiness.

Q4 2026 exploring

Cross-product audit

Measure token drift across enterprise apps. Consolidate variants back into @brandos/ui.

auditconsolidation
Q4 2026 exploring

Density modes

Compact vs comfortable densities driven by tokens. Only if enterprise users need them.

enterprisedensity
2027+ exploring

Tokens-as-data API

Serve tokens as a versioned JSON feed so downstream tooling (Figma plugins, CI checks) can pin exact versions.

platformapi

04 · Proposals

How to propose an item

The roadmap is a living doc. New items land via the same path any engineering spec does.

  1. 01
    Draft a one-pager. Problem, users affected, shape of the fix, token / component implications. Link mocks if you have them.
  2. 02
    Discuss in planning. Tag dependencies — Figma access, library release trains, app upgrades — and a rough sizing.
  3. 03
    Capture the outcome here. Accepted items land on this page with a quarter and a status. Track execution in the linked tracker.