Model public structured content, create a parameterless saved View, mount that View in a Component, and export the result as site content. Current Content files share the table editor but intentionally exclude runtime write actions and restricted access.
Coverage: UI + MCP. Content is evaluated for export; use a Database table when the shipped application needs runtime writes or identity-based access.
Use Content for public data that can be baked into generated site output: articles, features, navigation, FAQs, team profiles, or catalog information that does not require a runtime identity.
Use a Database table when the application must insert, update, or delete records at runtime, accept action parameters, or restrict data to signed-in users or roles.
Content is the current CMS format. Legacy CMS Model/Data files can still load old projects, but they are not the route for new content.
Create a Content file in the CMS area.
In Model, add typed columns with intentional names and compatibility rules.
In Data, add representative records and verify formatted values.
In Actions, add a saved View.
Configure its returned fields, filters, sorting, grouping, aggregates, and row limit.
Preview the View and check the actual returned shape.
Every Content action is a public, parameterless View. Insert, Update, Delete, runtime parameters, writable/default fields, and restricted access are removed or refused by the Content model.
Open the consuming Component and switch to Logic.
Use the View mount for the Content file and saved View.
Bind fields to text, images, attributes, or nested Component props.
Use repeat behavior for list results and an intentional key.
Design empty and missing-media states.
Preview representative records, then inspect generated output.
mount-view is the Content/database route. mount-data-source is reserved for API and Storage mounts.
In the
Websiteproject, inspect<Content file reference>and<Component reference>. Add or reuse columns<schema>, add only these documentation-safe rows<rows>, and create a public parameterless View named<name>with<filters/sort/fields/limit>. Mount that View in the Component, repeat<item element>, and bind<fields to targets>. Preserve every unrelated column, row, View, and logic branch. Verify the View result, repeat/bindings, Preview, and generated output. Do not create a write action or include private data.
The table-* family addresses Content schema, records, Views, aggregates, identity, and Preview. The Content model itself rejects database-only action capabilities even if a caller requests them.
confirm the file is the typed current Content format;
preview the saved View rather than only the working Data grid;
verify returned fields and record ordering;
test zero, one, and several records in the Component;
inspect repeat keys and missing-value behavior;
inspect the generated content payload and resulting site pages;
re-export after a content change and verify the destination diff.
Content record edits can be offered to a running Preview through its update flow, allowing a deliberate refresh instead of resetting Preview state on every keystroke.
Schema/View definition edits and record-value edits are persisted table changes, though the UI distinguishes definitions from data for Preview updates. The Component mount is another file's content change. Verify and undo each file separately.
Export writes the evaluated content to an external destination; file undo does not remove or roll back that output.
Content Views are public and parameterless.
Content has no runtime Insert, Update, or Delete action.
Restricted or signed-in access belongs to Database, not static Content.
Relations and media references must continue to resolve.
Generated output can become stale until it is exported again.