Publish a Page, Section, or Symbol to make your content available to others. Learn to:
- publish your content
- solve common issues that may arise
To display published content on your web application, you must have already integrated your application with Builder. For more details, visit the Publish Overview or Publish Quickstart.
To publish a content entry:
- Go to a draft content entry, or create a new one.
- Update text, styles, and more within the content entry.
- Click the Publish button.
Publishing a content entry makes it accessible to standard API calls and should make it visibly accessible on your web application, if integrated correctly.
The best way to verify your content entry has been published is to visit your web application where you expect the content entry be.
If needed, you can also verify the current status by of a content entry by making an API request.
Make an API request to the URL below, replacing <model> with the name of your model and <api-key> with your Public API Key. For more details, visit Content API.
https://cdn.builder.io/api/v3/content/<model>?apiKey=<api-key>The Builder API updates immediately upon clicking the Publish button, so you should get your content entry within the API response.
If you've published a content entry, confirmed that your pages are properly integrated, checked the entry has been published through the Content API, but it still isn't showing up on your web application, the issue is usually related to caching rather than Builder itself.
Builder's content API typically returns the updated content correctly, but various caching layers can prevent these changes from reaching your users.
Potential solutions for how to solve this are included below.
Your framework may implement defaulting caching. This may interfere with Builder's APIs.
For example, if you're using Next.js, aggressive caching settings can cause this issue. To solve it:
- Review your Next.js caching configuration.
- Opt out of aggressive caching by following Next.js caching documentation.
- For SSG with ISR, ensure your revalidation settings are appropriate.
- Update cache-control headers to reduce caching duration, for example:
res.setHeader("Cache-Control", "s-maxage=10, stale-while-revalidate=60");.
If you're using Vercel, this is the most likely cause. Vercel has its own data cache that can prevent updated content from appearing.
- Go to your Vercel dashboard.
- Navigate to your project.
- Find the Data Cache or cache management section.
- Purge the cache following Vercel's documentation.
Alternatively, trigger a fresh build and deploy.
CDNs can also implement their own caching protocols. For example, if you're using AWS CloudFront:
- Open your AWS Console and navigate to CloudFront.
- Select your distribution.
- Go to "Invalidations" and create a new invalidation.
- Enter
/*to invalidate all cached content.
Then, wait for the invalidation to complete.
If you're using Static Site Generation (SSG) with Incremental Static Regeneration (ISR), try the following:
- Trigger a fresh build and deploy.
- Request the specific page URL directly in your browser to force ISR.
- Check your
getStaticPathsandgetStaticPropsconfiguration, especially the revalidate setting.
For more details on integrating content entries into your web application, visit the Publish Overview or Publish Quickstart. To learn more about how to directly access Builder's APIs, visit the API intro or Content API.