Campaign Landing Page Rollout with Shared Content and Localized Variations
A global retailer is launching a seasonal campaign across 12 locales. Each locale needs a landing page built from the same template, but with localized hero text, currency-specific pricing components, and region-specific legal disclaimers. The template currently has a single 'hero' component and a 'pricing' component that pulls from a shared price list. The marketing team wants to avoid duplicating the entire page structure for each locale, but they also need the ability to override the hero text and pricing display per region without affecting other locales. The legal team requires that disclaimers be centrally managed and updated in one place. The site currently uses editable templates and a mix of static and dynamic components. The rollout must be completed in two weeks, and the content authors are not developers.
1. What template and component strategy would you recommend to meet the localization and central management requirements without duplicating page structure?
Read the worked answer
Use a single editable template with a structure that includes a responsive grid and policy-controlled components. For the hero, create a custom component that supports inheritance: the base content is defined in a shared experience fragment or a global content fragment, and each locale page can override it via a component dialog that allows authoring a local value. For pricing, use a component that reads from a central price list (e.g., a JSON data source or a content fragment model) and filters by locale context, so authors don't manually enter prices. For legal disclaimers, use a content fragment or experience fragment referenced by all pages; updates to the fragment propagate automatically. This avoids duplicating the page structure, keeps authors in familiar dialogs, and centralizes updates. The template should have policies that lock down certain components to prevent accidental changes, while allowing overrides where needed.
2. How would you handle the requirement that disclaimers be centrally managed and updated in one place, while still allowing locale-specific variations if needed?
Read the worked answer
Create a content fragment model for disclaimers with fields for text and locale. Store all disclaimers in a single content fragment folder. On each page, include a component that references the appropriate disclaimer fragment based on the page's locale (using a locale selector or a page property). If a locale needs a variation, create a new fragment for that locale and reference it; otherwise, use a default. This centralizes management: legal updates the fragment, and all pages using it reflect the change. For variations, authors can create a new fragment and update the reference on specific pages. Alternatively, use experience fragments with variations per locale, but content fragments are better for structured text. Ensure the component caches appropriately and that the reference is resolved at render time.