The curator approves it
An agent that can publish is an agent that can embarrass you. In Shio the division of labour is explicit: the agent builds, and the curator approves, corrects and tweaks. Every agent write lands as a draft by default; publishing is a separate, gated act; a destructive operation needs a confirm token naming exactly what it will remove; and a delete is a trash you can undo, not a hole in the site. Who changed what is attributed, and a review queue is there for the changes you want to see before they go live.
The same rule covers what your visitors send you: a form submission arrives as a draft post of a type you already modelled, so it is visible to a curator and invisible to readers until somebody publishes it. There is no separate submissions inbox to learn, and nothing new decides what "approved" means, the review queue you already have is the moderation step.
The console is where that curation happens, browse the content tree, edit a post through the form its post type declares, move and copy with both ends authorized, compare a draft against what is published and restore an older version, schedule a publish for later, and manage the media library. For the pages a reader actually sees, the Universal Editor puts the editing surface on the rendered page itself: click the text, fix the wording, save it back. And a preview link shows the draft exactly as it will look, before anyone else can see it.
Three pages carry most of that. The content console is the screen you are in every day: the browser, the post form, the Media Library, copy and move, what "select everything" actually selects, and the trash. Preview, history and scheduling is the half of the safety model that only helps once you know it exists, how to share a draft without publishing it, what changed since the last publish, and how to put a bad edit back. Content in several languages is worth reading before the second language, because a translation is a sibling post with its own URL and that decides your URL structure.
The content console
The surface a curator is in every day in Viglet Shio: the content browser, the post form, copy and move, selecting more than one thing, and the trash.
Preview, history and scheduling
The Viglet Shio curator's lifecycle tools: share a draft with a preview link, compare a draft against what is live, restore the published version, schedule a publish, and read the audit trail.
Letting an agent in
What stops an agent from surprising you: draft-default writes, dry runs, confirm tokens, the review queue, attribution, the trash, and the gaps that are still open.
The Universal Editor
Edit the rendered page: annotate a template with sh-field, open the page in the console, click the text and save it back to the draft.
Content Modeling
Post types in Viglet Shio: one name-keyed surface, the widget catalogue, relationships, the model as code in TypeScript or JSON, and renaming without losing content.
Content i18n
The locale axis in Viglet Shio: every post carries a locale, a translation is a linked sibling post with its own URL, the CDA's ?locale, the locale segment in delivery URLs, and the template helpers that render a language switcher.
Administration
The operator's half of the Viglet Shio console: the dashboard, users, groups, roles, permissions, API tokens, tenants, providers, email, webhooks, activity and the agent review queue.
Import & Export
Exchange providers, content migration, and site backup/restore in Viglet Shio CMS.