FAQ 8 · Proof split

Proof Split FAQ

Compact product signals reinforce the introduction while the larger Grid column remains dedicated to readable answers.

Built for delivery

A system teams can trust

The foundation is small enough to understand and complete enough to carry real product work.

53documented components

AAaccessibility baseline

3supported themes

0framework lock-in

Are all components documented?

Yes. Every primitive, composite, and pattern has a colocated contract covering markup, public tokens, states, accessibility, and tests.

How does the library avoid framework lock-in?

The public surface is vanilla HTML, CSS, and JavaScript, with optional Light DOM custom elements for progressive behavior.

What does the accessibility baseline include?

Semantic elements, keyboard behavior, visible focus, readable contrast, reduced motion, and automated browser checks are required.

Can the system scale across products?

Yes. Semantic tokens and layout primitives create consistency while documented component tokens preserve controlled product-level variation.