Data Model & API¶
The content model and the API contract the mobile app consumes. Some of this is shipped and some is still design ahead of the build — each page carries a status admonition at the top. For the why behind the shape, see the Design Rationale; for the settled what, the other four.
-
CMS Architecture
Canonical content model — collections, fields, the tag-overlap graph, and traversal.
-
Database Schema
Column-level schema + ER diagram for content, journeys, and progress tables.
-
Journeys & Home
Design for the Journey spine, Home feed slots, theme system, and their API.
-
Mobile API Contract
Mock contract with full request/response examples for the FE team.
-
Design Rationale
The reasoning behind the model — separate vs unified types, global themes, computed edges.