Skip to content

Navigation and pages as data

What the app shows is data, in two layers kept apart:

  • the navigation structure — what exists and how it is grouped: a tree of entries, each opening a built-in view or a page, or holding children. It means the same to every client (the TUI reads the same structure).
  • the representation profile — how this browser draws each level: tab bars, sidebar sections, links, nested entries. It never goes into the structure.

And the views themselves are mostly pages: JSON documents rendered from a fixed catalog of components over declared data sources.

Keeping the two layers apart is what lets the web app and the TUI share one structure: an admin shares a structure once on the context (cfg.navigation) and both clients follow it, each drawing it its own way, and a user may keep a structure of their own that takes precedence in their client. Pages work the same way: a page is a document, validated against a catalog every client knows, so it can be built by hand, generated by AI, shared on a context, or shipped as a built-in view, and it renders the same everywhere.

The fields, the editor and the catalog: Pages and navigation.