Target shards
Pick one or more shards. Deploy to a test tier before prod.
Central drafts → snapshot → S3 → shards. Signed in as staff.
CONTENT_BUCKET (+ IAM access) and restart.
Pick one or more shards. Deploy to a test tier before prod.
Select the drafts to diff or deploy. Maps deploy the branch chosen in their picker.
Per shard, grouped by content domain, then per draft: exactly what deploying the ticked selection would do — placements and spawners added/removed/changed, def fields old → new, tile edits as counts. Bulk edits fold into counted lines you can expand for the precise list; the raw draft JSON stays one click away per entity.
Recent snapshot versions per shard (from the deploy audit; S3 listing as fallback). Rolling back repoints the shard's manifest at an older snapshot — the confirm shows exactly what would change.
Pull content out of a shard's CURRENT snapshot into the central drafts
(seed for editing / redeploy). Map imports land on the
main branch. Comma-separate ids.
One locale's whole translation block as JSON —
{"<contentId>": {"<fieldPath>": "text"}}.
Load a locale (or import i18n:<locale> from a shard
snapshot above to start from live), edit, save — then tick it under
Translations in the drafts list and deploy like any draft.
Deploys replace the locale wholesale.