Fallback content
Understand how fallback content keeps your application resilient.
Fallback content is what your application renders when dynamic content is unavailable due to network failures, downtime, unexpected errors, or when you suspend the service manually. It acts as a safety net, ensuring your users always see meaningful content regardless of external conditions.
Where it lives
Shipping fallback content with your application ensures your users always have something to see, even in worst-case scenarios like network outages or API downtime. You can define it directly in your source code where you fetch the slot content, or use the CLI to generate it automatically.
When you add a slot using the CLI, it automatically downloads the default content and makes it available to the SDK as fallback.
Sync strategies
Because fallback content lives in your source code, it can become outdated as you update content in the platform. There are two common ways to keep it in sync:
- Using the CLI: The CLI can automatically sync the fallback content with the latest slot default content.
- Using a CMS: If your application uses a CMS, you can use its content as fallback, giving the marketing team autonomy to update it without requiring new deployments.