Releases

Updated component and token references

Date: 2026-10-03
Type: Documentation

The public Storybook reference now gives Button, Alert, and Icon focused documentation, interactive Playgrounds, and copyable usage examples. Examples retain the surrounding markup needed for the demonstrated behavior while excluding documentation-only presentation wrappers.

Foundation pages provide searchable token tables with CSS references, resolved values, previews, and role descriptions where useful. Tables preserve their columns and scroll horizontally on narrow screens. The shared theme toolbar applies to both component documentation and Foundation references.

Explore the component reference or browse spacing tokens.

Alert 0.3.0

Date: 2026-09-24
Type: Component release
Package versions: @jangle-ui/components@0.3.0, @jangle-ui/contracts@0.3.0, and @jangle-ui/knowledge@0.3.0

Alert adds persistent feedback for the task or content region a person is working with. It supports information, success, warning, and danger tones, an optional heading, and a plain-text message. Announcement urgency is independent of tone and defaults to polite.

When a failed automatic load needs a distinct recovery command, an application can supply one existing Button inside the Alert. Button handles its pending behavior; the application handles the request and result. Alert does not move focus, dismiss itself, or add a second outcome announcement.

The release includes the component contract, native Storybook examples and Controls, a usage guide, and installed coding-agent guidance. Explore Alert in Storybook.

Button 0.2.0 is available

Date: 2026-09-07
Type: Component release
Package releases: @jangle-ui/components@0.2.0, @jangle-ui/contracts@0.2.0, and @jangle-ui/knowledge@0.2.0

Jangle UI now includes a released Button for actions with a visible label. Teams can use one consistent control for ordinary actions, saving or loading behavior, and form submission instead of rebuilding those states in every application.

What customers get

• neutral, brand, and destructive appearances with clear emphasis choices,
• small, medium, and large sizes with an optional leading or trailing Icon,
• native keyboard and focus behavior,
• disabled and saving or loading states that prevent accidental repeat activation,
• native submit and reset behavior, including submitter names, values, and form overrides,
• and version-aligned component contracts and coding-agent guidance.

Read the Button guide, explore the complete public Storybook reference, or manage a subscription and package credential. The released-package verification app shows Button and Icon installed from the protected registry; its surrounding shell, table, and form fields are custom application code rather than additional Jangle UI components.

Icon system completed

Date: 2026-09-06 Type: Component and architecture Package release target: First 0.1.0 Components, Contracts, Icons, and Knowledge package line

Jangle UI completed its first component vertical slice with direct Lucide catalog access, a small portable system layer, and a standards-based Web Component.

Included

• every provider-native name in the pinned Lucide catalog, usable directly from Lucide documentation,
• a 14-name system:* subset for portable Jangle component meanings,
• local on-demand Lucide modules with no CDN or runtime network request,
• alternative-provider validation, deterministic Lucide fallback, and application-owned app: extensions,
• the non-interactive <jangle-icon> component with token-mapped named sizes, inherited color, decorative and meaningful semantics, logical RTL mirroring, and observable missing-name behavior,
• separate class-only and explicit registration entry points,
• native Storybook stories, select controls, attached MDX guidance, size examples, accessibility examples, fallback behavior, a full-catalog select, and the portable system aliases,
• generated Custom Elements and semantic contract artifacts,
• installed package and coding-agent guidance, bundle ceilings, and clean packed-consumer coverage.

This release does not add Button, Icon Button, Forms, layout primitives, or other dependent components. Those remain behind their existing architecture and founder-selection gates.

Token foundation completed

Date: 2026-09-03
Type: Design-system foundation
Package release target: First 0.1.0 package line

Jangle UI completed the supported foundation that will support its first versioned token release.

Included

• complete public Color, Typography, Radius, Stroke Width, Opacity, Elevation, and Motion contracts,
• public Spacing and Size coordinates for whitespace and occupied dimensions,
• generated CSS, typed JavaScript and TypeScript, and machine-readable JSON for the complete supported catalog,
• independent Brand, Neutral, Surface, Shape, and Appearance theme choices with a complete default theme,
• deterministic repository-local theme generation through the token compiler,
• private reference palettes and internal theme roles excluded from consumer artifacts,
• reconciled Figma variables and styles for the supported semantic foundations,
• accessibility and semantic-relationship validation across supported color configurations,
• and clean installation and execution from packed package artifacts in vanilla and React consumers.

This completes the local token release candidate. Protected Cloudsmith prerelease verification, external reference-consumer upgrade, and release promotion remain release operations rather than new foundation design work.

Hosted commercial journey verified

Date: 2026-08-20 Type: Platform history Package releases: Protected prerelease 0.1.0-prerelease.0 and candidate 0.1.0-prerelease-e4454c5f75ad1b4aa37b6a1c9c675f2ef37c735a

Jangle UI completed the first uninterrupted hosted subscription and protected-install journey in the staging environment.

Included

• hosted email authentication through the scanner-safe confirmation flow,
• Stripe Managed Payments sandbox checkout,
• signed webhook activation of the application-owned entitlement,
• one-time Cloudsmith download-credential issuance,
• clean installation and execution of @jangle-ui/components@0.1.0-prerelease.0,
• end-of-paid-period cancellation scheduling with access preserved through the paid period,
• terminal Stripe cancellation with webhook-driven entitlement and Cloudsmith credential revocation,
• denial of a fresh protected install after revocation,
• continued execution of the package installed before cancellation,
• publication of an immutable second prerelease tied to its staging commit,
• upgrade of the separate vanilla reference repository through the protected registry,
• independent GitHub Actions and Vercel preview verification,
• promotion of the verified consumer state to its main-branch Vercel deployment,
• independent static hosting of the Storybook workbench through its own Vercel project,
• connection of jangleui.com, staging.jangleui.com, and components.jangleui.com to their production, staging, and workbench deployments,
• permanent redirection of www.jangleui.com to the production apex,
• environment-aligned Supabase Auth and application URL configuration,
• and signed Stripe webhook delivery through the owned staging hostname.

The package-delivery critical path through external consumer upgrade is now operational. Stable package publishing remains intentionally disabled pending the stable release gate.

Hosted delivery foundation verified

Date: 2026-08-18 Type: Platform history Package release: Protected prerelease 0.1.0-prerelease.0

Jangle UI connected and verified the first hosted commercial-delivery foundation without claiming a stable customer release.

Included

• isolated US-East Supabase projects for non-production and production,
• Vercel production and stable staging deployments with environment-specific credentials,
• a signed Stripe sandbox webhook processed by the hosted platform,
• private Cloudsmith staging and production package repositories,
• isolated Cloudsmith runtime identities and a write-only release publisher,
• five protected prerelease packages published after the full remote verification suite,
• an authenticated package-manager install using a one-time customer entitlement token,
• and verified denial of fresh artifact downloads after credential revocation.

Stable package publishing, live Stripe billing, owned-domain connection, and the continuous hosted customer journey remain gated work.

Phase 0 foundation begins

Date: 2026-08-17 Type: Platform history Package release: No

Jangle UI established its repository, product-platform architecture, documentation model, release boundaries, and protected-delivery integration points.

This entry starts the public chronological product history. It does not claim that a customer-ready component library or paid subscription is available.

Included

• monorepo and package boundaries,
• public platform and hosted documentation shells,
• account, billing, entitlement, and registry service boundaries,
• Storybook and package-consumer proving surfaces,
• versioned component-contract and agent-knowledge pipelines,
• Changesets and CI release governance.