Stage 3 – Localization Management PM-owned portal + governed publishing to CDN

Product can ship copy changes without engineering

Build on Stage 2’s remote packs and add a Localization Management System (LMS): a portal where product teams can add/update key-value pairs, trigger a governed publish, and see changes reflected in client apps via the same CDN delivery and device caching.

Localization Portal

Edit translations like content

PM/Design
Key editor structured

Add new keys, update wording, attach context (screenshots / notes), and manage locales.

Workflow governed
  • • Draft → Review → Approved
  • • Optional: translator + linguistic QA
  • • Publish creates a new immutable bundle version
Permissions roles

Role-based access (viewer/editor/reviewer/admin) to prevent accidental production changes.

What engineers still own

The platform: validation rules, publishing pipeline, bundling, CDN distribution, monitoring, and rollback.

Validation Publishing Observability Rollback

Publishing pipeline

Turns edits into a versioned, CDN-distributed translation bundle.

  1. 1
    Edit in portal
    Update key(s): profile.edit_photo
  2. 2
    Validate
    Checks: missing keys, placeholders, plural rules, RTL, length limits
  3. 3
    Approve (optional)
    Review + audit trail for compliance
  4. 4
    Bundle + version
    Generate immutable packs: v2026.02.08-7f3a
  5. 5
    Publish to cloud → CDN
    Edge caches warm organically (or via pre-warm job)
  6. 6
    Clients consume updates
    Apps pull latest bundle version via config/bootstrap

How clients detect updates

Bootstrap config lightweight 
{
  "locale": "es-ES",
  "fallbacks": ["es-ES", "es", "en"],
  "i18nVersion": "v2026.02.08-7f3a"
}

If device cache version differs, download the new pack from CDN. Otherwise keep using cached resources.

Delivery stays the same

Stage 2 CDN pattern + device cache

Stable
Immutable packs cache-friendly

Published bundles are immutable per version, so CDN caching is safe and predictable.

Two-layer caching edge + device

The edge serves most requests quickly. The device keeps the last used packs for instant startup and offline use.

Safety & governance

  • Audit log for every change (who/what/when)
  • Rollback by switching i18nVersion in config
  • Validation rules prevent broken placeholders and missing keys
  • Optional approvals for sensitive surfaces (legal, payments, onboarding)

Pros

  • PMs/designers can update copy in minutes
  • No engineering bottleneck for wording iterations
  • Safe rollout with versioning and rollback

Cons

  • More platform complexity (portal + workflow + validation)
  • Requires governance decisions (who can publish, approval rules)