Content Studio is the authoring environment for passport content. It is where editors decide what appears on a passport — the sections, the field selection, and the prose that wraps regulated data.
When the same underlying field is reachable via more than one alias (for example, the deprecated core.identity.brand_name aliasing the canonical core.identity.product_brand_name), Content Studio deduplicates the field at edit time so the editor only ever sees a single, canonical entry. Deprecated aliases are read-only and surface a deprecation hint.
Content Studio uses a draft tree that is persisted as you work. Drafts are workspace-scoped, never published implicitly, and follow a strict sync-on-publish model — content is written into the live passport configuration only when the editor explicitly publishes.
Available sections are derived from the brand’s industry classification and the DPP Field Catalogue. Up to 15 sections can appear on a passport. Section order can be reordered within Content Studio.
Content Studio is concerned with what is presented. Theme Studio is concerned with how it is presented. The two surfaces are intentionally orthogonal — changing content does not change visual design and vice versa.