Appearance
Content & media
What the Content, Pages, Page chrome, Media, Corpus, and Content tags screens manage — and why NanaSelect carries its own content layer at all.
What it is
Six admin surfaces manage the app's editorial layer:
- Content (
/admin/content) — the content home: one inventory of every piece of app content — CMS-authored pages alongside code-routed copy slots — each with its publish state, so an editor sees what's live, drafted, or unset in one place. - Pages (
/admin/pages) — the CMS half: fully CRUD-able pages published at/<slug>, with a draft → published → retired lifecycle. - Page chrome (
/admin/page-chrome) — the copy and media for fixed, code-routed surfaces (home hero, banners): the route is code, the words and imagery are data. - Media (
/admin/media) — the media library: assets at Drupal scale (tens of thousands), organised by tagging so pickers stay usable. - Corpus (
/admin/corpus) — the Product Expertise Corpus: NanaWall product literature (PDPs, blog posts, brochures, case studies) ingested so the engine can explain its recommendations, grounded in real material. - Content tags (
/admin/content-tags) — the enrichment review queue: auto-proposed facet tags on corpus content, human-reviewed before going live.
Why it exists
Structured data says which system fits; content says why — and teaches the trade-offs along the way. The corpus exists so recommendations can cite genuine product literature instead of generated copy, and enrichment tags that literature with the same facet vocabulary the guided flow uses, so relevant content surfaces at the step where it helps ("educate through every step" — see why it works).
The editable copy layer (pages, chrome slots) exists for pace: marketing copy changes far more often than routes do, so words and imagery are data an editor publishes, not code a developer deploys. The single content inventory exists because two structurally-different kinds of content (CMS pages, code-routed slots) still need one editorial picture — see the content model for the two dimensions and why they don't overlap.
In the admin
| Screen | How-to |
|---|---|
| Content | The content inventory |
| Pages | Managing pages |
| Page chrome | Managing page content |
| Media | Managing media |
| Corpus | Managing the corpus |
| Content tags | Managing content tags |
Learn more
- Content model · page sections · CMS public rendering.
- Corpus data model · ingestion · retrieval.
- Media tagging · media presentation · content enrichment.
- The DAM spin-off framework — whether/when media leaves NanaSelect for a standalone DAM.