Content is the current CMS format: a typed table whose public, parameterless Views are evaluated for generated site output.
Property: Identity · Current behavior: stored metadata type cms-content
Property: Creation · Current behavior: Create Content in CMS or nested CMS folders
Property: Workspace · Current behavior: shared table Model, Data, Actions, and Inspector
Property: Actions · Current behavior: View only; public and parameterless
Property: Component use · Current behavior: create a View, then mount-view
Property: MCP · Current behavior: table-* family with Content restrictions enforced
Model typed columns and relations; edit records in a virtualized grid; define saved Views with filters, sorting, grouping, aggregates, returned fields, and row limits. The same table interface is used as Database, but Content removes runtime Insert/Update/Delete, parameters, writable/default fields, and restricted access.
Use Content for public export-time information. Use a Database table for identity-based or runtime write behavior.
The table read/schema/row/View/aggregate/preview operations apply. The Content model refuses or strips database-only action options even if requested. Mount saved Views in Component logic with mount-view, not the API/Storage mount-data-source route.
Content is baked into generated output and must be re-exported after relevant changes. Test zero/one/many records and missing values. Every View is public; never store private data expecting an access rule.
Definitions and records persist as table data; Preview can offer an explicit Update rather than reset state on every cell edit. External exported files need destination-specific recovery.