Headless 360Intermediatecmscontentheadlesscommerce
Implement content delivery for headless storefronts with CMS
Real World Scenario
Marketing manages hero banners and promotional content in Salesforce CMS but Next.js storefront shows stale content for hours.
Expected Answer
• Use CMS Delivery API with webhook-triggered cache purge on publish
• CDN cache keys including locale and market segment dimensions
• Preview API for staging content before production publish workflow
• Fallback to last-known-good content when CMS API unavailable
• Structured content models mapping CMS components to React component library
• Schedule-aware content respecting campaign start/end datetime metadata
• Monitor CMS API latency as part of page performance budgets
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Use CMS Delivery API with webhook-triggered cache purge on publish. CDN cache keys including locale and market segment dimensions. Pick based on your integration pattern and team capability. Content freshness is operational concern—architect publish-to-CDN pipeline with measurable SLA, not manual cache clears. Balance speed of delivery with maintainability.
Architect Perspective
Content freshness is operational concern—architect publish-to-CDN pipeline with measurable SLA, not manual cache clears.