CONCEPT Cited by 1 source
Cross-surface content unification¶
Definition¶
Cross-surface content unification is the property that a single piece of domain data — rendered in multiple product surfaces (landing page, product detail page, email campaign, mobile app deep link, …) — resolves to identical values by construction, because every surface reads it from the same backend.
The architectural pattern that achieves this in a CMS-plus- aggregation-tier architecture: CMS entries hold IDs for domain entities; the aggregation tier or its proxy enriches the IDs with values from the system of record; the system of record is also what every other surface reads.
Why it matters¶
Without unification, the same logical object (a sustainability-certificate description, a product price, a brand biography) is duplicated across the CMS, the PDP backend, the search index, and the campaign-email template. Duplication in a multi-market environment (Zalando operates in 25 languages) multiplies linearly with language count and goes stale unpredictably. Legal-sensitive claims (e.g. sustainability certifications) make staleness a compliance risk, not just a polish problem.
Canonical wiki instance — Zalando Sustainability Certificate¶
In Zalando's Landing Pages stack (Source: sources/2022-09-28-zalando-more-editorial-content-please):
- A Sustainability Certificate module in Contentful stores only certificate IDs (plus intro copy — title, subtitle, description — which is editorial).
- At request time, the
Contentful proxy calls
the same backend that serves the Product Detail
Page's sustainability accordion and enriches the
response with each certificate's
logo.uri,title, anddescription. - A certificate shown on a landing page and the same certificate shown on the PDP therefore carry identical values — "always in sync".
Quote: "Using a single source for sustainability information is valuable not only for making the life of our Content Editors easier (especially when considering the number of supported languages), but also because it's important to show accurate and up-to-date information about Sustainability claims across the whole customer journey."
The underlying split¶
- CMS holds editorial context — the which and the framing. Which certificates show up on this sustainability landing page. What the intro paragraph says.
- System of record holds domain values — the what. What GOTS stands for. What its logo looks like. What the definition of "Made with 70–100% recycled materials" is.
The boundary matters: editorial context should be authorable by non-technical staff in the CMS; domain values should be maintained by the team that owns the domain (and reflected uniformly wherever the domain surfaces).
Related pattern¶
patterns/cross-surface-enrichment-via-internal-service is the concrete pattern. The aggregation tier's proxy is the join point.