Author in context. Stay with the work.
Studio is the target page builder and content editor for Kumwe: layout, blocks, typed fields and values in one resource-bound workspace. That end-to-end App journey is not complete yet.
One workspace, not a catalogue hand-off.
Creating or editing managed content should open Studio for that exact item, preserve its authority and unsaved state, and support clear outcomes for saving the item or creating reusable types.
Strong primitives are already connected.
App has a compiled Studio shell, a Blueprint canvas, authenticated PHP host dispatch, bounded content context, persistence, media, preview, localisation, telemetry and extension-contribution primitives.
These primitives are valuable infrastructure; they are not evidence that the complete contextual-authoring journey has passed.
Content creation and editing still cross separate forms.
The current App route opens a Blueprint-only composition view from an existing content-type version. Blank or reusable-type creation, entry editing, field creation, explicit save outcomes and the full context-preserving acceptance journey remain open.
The browser presents; App remains authoritative.
Studio’s browser assets are compiled before deployment. PHP application services retain authentication, authorisation, validation, revision, transaction, idempotency and audit authority; production does not require a JavaScript server.
Track the integrated journey in public.
Studio and App publish separate contract and implementation status so target, primitives and completed acceptance are never conflated.