Backend data structure and test-data design docs — schema proposals for
in-progress features, ahead of or alongside implementation.
Available docs
Theme Token Inheritance Model — sparse-override inheritance (Site → Page), with inline token overrides at Container/Item, for the MEC Admin theming tool's token/theme data.
Theme Data Structure — Schema Reference — the same model as field/table reference: ThemeNode schema, scopeType tiers, a worked UAL example, and the full 45-token catalog.
Theme Model — Future Extensibility — extension points worth designing room for now: token aliasing, a token type/lockable registry, orthogonal axes (locale/platform), draft/publish across a cascade, resolved-token caching, version history, and token schema migration.
Admin Tool → Content Pipeline: Gap Analysis — checks the "Admin feeds JSON, backend places containers and associates items" mental model against the shipped Dynamic Feed, Content, and Theme Endpoint contracts; identifies what's missing.