Content & data

The app's content tools let you browse and edit everything in a site's database — both the content the site author manages and the data visitors submit — without touching code.

Browsing and editing

For each table you can list, view, and edit individual records. This is how a site owner keeps content current — updating a product, publishing an article, fixing a listing — and how you inspect the data a site is collecting.

Submissions and approvals

Where a table holds user-generated content behind an approval queue, the content tools are where you review, approve, or reject submissions before they go live. Deleted records can be restored within their recovery window, and you can see what depends on a record before removing it.

From the CLI

Runtime tables are also manageable from the command line with acira db — query, get, create, update, delete, approve, restore, and export rows — which is handy for scripting and bulk work. See the CLI.

Content vs. code

Editing records changes a site's data, not its code. Structural changes — adding a field, changing a table's schema — are part of the site project and go out through a publish. Keeping the two straight avoids surprises: content edits are immediate; schema changes ship with a deployment.