Changelog

Authors can see whether an edit is in flight, confirmed, or failed — Saving, Saved, and Not saved states appear directly in the editing bar so changes are never silently lost.

“Not saved” persists until resolved with no auto-hide; a related bug where stale save state could leak across instance switches is also fixed.

The sign-in button and account avatar now live in the top navigation bar, matching the standard information architecture with auth controls alongside search and nav.

Avatars now show initials as a fallback when no profile picture is set, and a stale loading state when navigating back from the sign-in flow is cleared automatically.

Agents and clients can go directly from list-patterns to get-pattern-specification without an intermediate get-pattern call, eliminating unnecessary large payload fetches.

Each pattern entry now includes a templates array with templateId, rendererId, and normalized TemplateInfo (exportName, codeSrcPath, and renderer-specific fields).

Toast notifications, banners, and spinners include ARIA live regions so screen-reader users receive feedback when content changes dynamically, addressing WCAG 4.1.3, 1.3.1, and 4.1.2.

Error messages interrupt immediately with role=“alert”; all other status messages use polite announcements. A new announce=“off” prop lets static banners opt out.

The account avatar stays visually highlighted for as long as its menu is open, giving a clear indication that the menu is active rather than dropping the focus style immediately.

The in-product Contact Knapsack menu item and floating support button have been removed as Zendesk is being retired.

Menus are now fully keyboard-navigable and correctly structured for assistive technologies, resolving WCAG 4.1.2, 1.3.1, and 2.1.1 gaps.

Fixes include correct aria-haspopup and aria-expanded on triggers, valid ARIA role nesting in nested menus, Home/End key support, and properly labelled combobox option groups.

The selected-state underline on primary navigation tabs now sits flush at the bottom of the header bar instead of floating beneath the tab text.

The Configure Asset Sets option is now a proper menu item reachable by arrow keys, and ArrowRight/ArrowLeft open and close the brand-group drill-down matching the WAI-ARIA submenu pattern.

Workspaces with asset sets spanning multiple brands get a cleaner picker: the asset set dropdown now groups options by brand, with a drill-down menu to navigate into each brand’s sets. Finding and switching to the right theme or style variation is faster, especially in workspaces managing many brands from a single design system.

Read about Asset Sets

Every customer can now plug these docs straight into their AI tools. The site runs its own MCP server, so Claude Code, Cursor, Claude Desktop, or any MCP client can answer from the live docs instead of stale training data — point your client at https://docs.knapsack.cloud/_mcp/server, or use the one-click Connect to Claude Code and Connect to Cursor buttons at the top of every page. For crawlers and agents that read Markdown, the site also publishes an llms.txt file at https://docs.knapsack.cloud/llms.txt, scoped per section so a tool can request just the part it needs.

AI tools querying component specs via MCP will now receive full props tables instead of empty responses, enabling accurate code generation from design system documentation.

Enriched inferred template specs were previously discarded before reaching the distro; they are now correctly rendered.

Read about Intelligent Tools

Component prop schemas are now correctly populated for sites with private app clients, fixing a silent failure that left all templates without enriched specs.

Keyboard users will now see a single, clean focus indicator on buttons, cards, and links instead of a doubled ring.

Pages and token editors that reference malformed color values (such as a bare #) now render gracefully instead of throwing an error.

Read about Design Tokens

Editors deleting a page, pattern, or tab now see a warning listing every page that links to it, preventing accidental broken links.

Publishing a branch with an open PR will no longer overwrite changes that were merged to the default branch in the interim.

Read about Branching and Publishing

Navigation, settings lists, and content blocks now show focus rings only for keyboard navigation, removing spurious outlines during mouse interaction.

A new LiveRegion component announces dynamic content changes to assistive technologies, and all form inputs automatically link error messages and character counts via aria-describedby.

Users with Viewer, Consumer, or Contributor roles on IPE-enabled sites can now connect to the MCP server; previously every non-admin received an HTTP 500.

Read about Intelligent Tools