Content Metadata¶
Purpose¶
This document defines the metadata layer that governs front-end structure, layout, and UI behavior across the Omnivoltaic site portfolio.
Metadata is not content data.
Strict Rule¶
No actual business or editorial data should ever be stored in metadata.
Metadata may describe:
- layout structure
- page composition
- block selection
- visibility rules
- interaction and UI behavior props
- routing and composition relationships
Metadata must not carry:
- product records
- article bodies
- contact submissions
- customer records
- quotations
- tickets
- tables of business rows
- any other live domain payload
Metadata Structure Types¶
The governed metadata object types are:
SitePageSectionBlockHeaderFooterBot
Object Responsibilities¶
| Type | Responsibility |
|---|---|
Site |
site-level identity, route tree, family membership, global behavior defaults |
Page |
route-level page selection, theme choice, page behavior props |
Section |
page subdivision and composition zones |
Block |
lowest reusable UI/content container selected by metadata |
Header |
top-of-site navigation and global entry behavior |
Footer |
bottom-of-site navigation and global exit/discovery behavior |
Bot |
governed conversational or assistant surface attached to a site or page |
Delivery Formula¶
Each front-end experience should be understood as:
front-end content = metadata + headless content + page behavior props
The metadata layer declares structure and UI behavior only.
Discipline¶
- metadata chooses what kind of object should appear
- headless content provides the live data to populate it
- page behavior props define how the page should behave
- downstream app code must not smuggle domain data into metadata to bypass BFFs