Design language
Designing the Gel Pop language
A practical account of how Gummy UI turns transmitted colour, attached reservoirs, stable reading planes, and restrained motion into one interface material.
By Gummy UI ·
18 original field notes
Design decisions, in the open.
Practical articles grounded in the implemented public component source, its documented behavior, and the work that still remains before production launch.
All articles
These articles explain current Gummy UI decisions without inventing customers, performance results, compatibility, or unavailable product capabilities. Subscribe through RSS.
Component architecture
Semantics before surface
How Gummy UI keeps native HTML or Base UI behavior in charge while adding editable React source, forwarded refs, and Gel Pop visual anatomy.
By Gummy UI ·
Registry guide
Reading a Gummy registry item
A field guide to Gummy UI’s public registry payloads, shared style dependencies, editable component files, and current installation verification.
By Gummy UI ·
Catalogue integrity
One catalogue, 57 component categories
Why Gummy UI derives its public component count, routes, source links, and registry names from a single catalogue instead of maintaining parallel claims.
By Gummy UI ·
State modelling
Documenting meaningful component states
A method for reviewing default, focus, filled, validation, disabled, read-only, selected, open, and responsive states without a decorative matrix.
By Gummy UI ·
Keyboard interaction
Keyboard contracts for overlays
How Gummy UI reasons about triggers, focus containment, dismissal, restoration, roving navigation, and non-modal surfaces across its Base UI overlay components.
By Gummy UI ·
Form foundations
Native forms with visible context
A close look at labels, descriptions, validation, read-only behavior, counts, groups, and form participation in Gummy UI’s public form foundations.
By Gummy UI ·
Bidirectional interfaces
RTL is behavior, not a mirror
How logical CSS, native direction, Base UI context, text alignment, reservoir placement, and keyboard expectations combine in Gummy UI’s RTL work.
By Gummy UI ·
Motion accessibility
Reduced motion without lost state
A component-level approach to removing travel, rotation, squash, and animated settling while preserving focus, selection, loading, and validation information.
By Gummy UI ·
Theme architecture
Building light and dark from semantic tokens
How Gummy UI separates canvas, surface, ink, focus, fruit families, and component-local material so themes can change without rewriting behavior.
By Gummy UI ·
Responsive design
Responsive components start with content
A practical approach to 320-pixel reflow, long labels, touch targets, logical stacking, bounded decoration, and container-driven component layouts.
By Gummy UI ·
Verification practice
Using the Component Lab as evidence
What Gummy UI’s Component Lab reveals, what automated tests add, and why a specimen page cannot replace browser and assistive-technology verification.
By Gummy UI ·
Accessibility testing
Testing accessibility in layers
How semantic assertions, keyboard tests, axe, contrast, responsive review, reduced motion, RTL, and manual smoke tests fit without overstating coverage.
By Gummy UI ·
Data interfaces
Composing data interfaces from primitives
How Table, Data Table, Pagination, Empty, Progress, Skeleton, Resizable, and Scroll Area divide semantic and visual responsibilities in dense interfaces.
By Gummy UI ·
Interaction design
Interactive cards need real elements
Why Gummy UI separates passive article cards, anchor cards, and button cards instead of attaching click and keyboard handlers to generic containers.
By Gummy UI ·
Machine discovery
Designing AI-readable component docs
How catalogue JSON, llms.txt, registry payloads, canonical pages, and explicit status language help agents discover Gummy UI without exposing private source.
By Gummy UI ·
Source governance
Keeping public and Pro source separate
The reasoning behind Gummy UI’s two-repository boundary and the practical rules for metadata, previews, registry payloads, releases, and credentials.
By Gummy UI ·
Product operations
Honest product status by design
Why Gummy UI separates specified, implemented, tested, deployed, and production-verified status across components, Pro, commerce, support, and legal pages.
By Gummy UI ·
Follow the source
Pair the editorial context with the component catalogue, implementation documentation, and editable-source registry. Product availability and launch gates remain explicit on the relevant status pages.