Deforking Phase 1 Implementation — Content from the Database (epic)

[seanmalbert]

• General
• Backend
• Public
• Partners

Background / Issue

Phase 1 of the Bloom deforking initiative moves per-jurisdiction content out of build-time files and
into the database, so the public site renders a jurisdiction's translations and structured content
from the API and jurisdictional admins can edit them in the Partners portal. This is the umbrella
issue tracking the work; the sub-issues below implement it.

Sub-issues:

• Key-level translation data model and migrations #6508 — Key-level translation data model and migrations
• Translation read/merge service and public read endpoints #6509 — Translation read/merge service and public read endpoints
• Translation admin CRUD (per-key) #6510 — Translation admin CRUD (per-key)
• JurisdictionContent service and admin CRUD #6511 — JurisdictionContent service and admin CRUD
• Permission model and flag gating #6512 — Permission model and flag gating
• HTML sanitization for rich-text content #6513 — HTML sanitization for rich-text content
• Public site hydration and ISR #6514 — Public site hydration and ISR
• Partners site hydration #6515 — Partners site hydration
• Partners translation editor #6516 — Partners translation editor
• Partners structured-content editor #6517 — Partners structured-content editor
• Staleness check in the missing-translations job #6518 — Staleness check in the missing-translations job
• Seed / data migration command #6519 — Seed / data migration command
• Rollout gating and staging-to-production promotion #6520 — Rollout gating and staging-to-production promotion
• Integration and end-to-end tests #6521 — Integration and end-to-end tests