frames
A UI component playground.
Components with their states laid out side by side — loading, empty, error, too-long-name — so the awkward one is visible before it ships.
every component shows its empty state first
Reordered the playground so the empty state is what you see before the happy path. It changed three components within a day.
frames v1.2.0 is out.
Three density tokens instead of a size prop on every component. Fewer decisions at the call site and one place to change your mind.
Checked every code sample in the frames docs against the current API. Nine fail. One issue with all nine rather than nine issues.
opened a discussion: what belongs in a component library and what belongs in your app. i have moved four things out of frames this month and the lib…
Every error message in frames has an id and is wired through aria-describedby. Screen reader pass recorded and linked in the pull request.