FAQ 7 · Editorial index

Indexed Editorial FAQ

Numbered disclosure rows give a longer answer set a clear reading order without adding decorative card chrome.

The operating guide

Start with the decisions that shape the system

Five practical answers explain how teams adopt, extend, and maintain Ren10.

01What belongs in the shared foundation?

Tokens, layout rules, reusable components, accessibility behavior, and documented product patterns belong in the shared foundation.

02When should a team add a component?

Add one when a repeated interaction needs a stable public API, named states, accessibility behavior, and a maintained contract.

03How are layout decisions made?

Choose a Ren10 layout primitive first, establish the responsive skeleton, and only then place components inside it.

04Can product teams override the theme?

Yes. Consumer themes override documented semantic or component tokens while internal component selectors remain untouched.

05What keeps the library reliable?

Contracts, automated checks, real browser testing, and visible examples keep implementation and documentation aligned.