CRUD-Sites¶
CRUD-Sites is the family for operational application surfaces.
These experiences are not public marketing pages. They are governed front-end systems with create, read, update, and delete workflows, role-based access control, and authenticated app shells.
Current CRUD-Site Portfolio¶
| Site | App URL | Status |
|---|---|---|
| Asset Admin — Distributor | assets.omnivoltaic.com | Active — first documented CRUD site |
Scope¶
- authenticated portal apps
- enterprise admin panels
- Odoo admin surfaces
- operational interfaces with role-based access
- legacy CRUD-oriented surfaces retained for completeness
Page Families Within CRUD Sites¶
CRUD sites may contain pages from more than one page family:
| Page Family | Used For |
|---|---|
crud |
Record list, record detail, record form, workflow steps |
metric |
Dashboards, telemetry views, events logs, indexed data |
auth |
Sign-in, sign-up, password reset |
onboarding |
Step-by-step first-run flows |
The Asset Admin — Distributor site uses crud, metric, and auth page families.
Delivery¶
CRUD sites are delivered by dirac-uxi-crud (planned). The UI stack is Mosaic-based, consistent with docs/governance/style-policy.md.
Governing Discipline¶
CRUD sites follow the same portfolio rule as all other families:
- metadata defines layout and UI behavior
- headless content and DTOs supply domain data
- app code consumes the declared contract rather than inventing its own
The intent schema for CRUD sites is docs/contracts/crud-intent.schema.json.
Child Site Pages¶
Each CRUD site has a human-readable spec under docs/sites/ and a machine-readable intent under docs/intents/sites/.