Skip to content

PATTERN Cited by 1 source

Cross-surface enrichment via internal service

Pattern

When domain data surfaces on multiple product pages (a landing page, a product detail page, an email campaign), store IDs in the CMS and enrich the IDs with values from the system of record at aggregation time. Every surface reads the values from the same backend, so they stay identical by construction.

The split

  • CMS holds editorial context — the which and the framing: which certificates to show on this landing page; which intro paragraph to display; which order to list them in.
  • System of record holds domain values — the what: the certificate's logo, its authoritative title, its canonical description, its localised translations.
  • Aggregation-layer (or its proxy) performs the enrichment join — takes the CMS response, extracts the ID list, calls the system of record, merges the values in.

Why it beats duplicating values in the CMS

  • Multi-market consistency. Zalando operates across 25 markets. Duplicating values into the CMS means maintaining 25 translations per value per surface and staying in sync with the system of record's updates — an unscalable operational burden.
  • Compliance. For legally-sensitive claims (sustainability certifications, ingredient lists, warnings), stale CMS copies are a compliance risk, not a polish problem.
  • Update propagation is automatic. When the system of record is updated — e.g. a new translation is added to the sustainability-accordion feed — every landing page using that certificate ID picks up the update without any editorial action.

Canonical wiki instance — Zalando Sustainability Certificate

(Source: sources/2022-09-28-zalando-more-editorial-content-please)

  • In a Sustainability Certificate module, Contentful stores title, subtitle, intro description (editorial), and a list of certificate IDs (referential).
  • The Contentful proxy maps the entry to the Collection GraphQL type via Collection.entities, then calls the same backend that serves the Product Detail Page's sustainability accordion to enrich each certificate ID with its logo.uri, title, and description.
  • A certificate shown on a landing page and the same certificate shown on the PDP carry identical values — "always in sync".

concepts/cross-surface-content-unification is the invariant this pattern delivers.

Last updated · 550 distilled / 1,221 read