Understanding Caching
Caching makes your site fast by serving pre-built pages instead of generating them from scratch on every request.
How ISR works
Your site uses Incremental Static Regeneration (ISR). Here is the flow:
- A visitor requests a page
- If a cached version exists and is fresh, it is served instantly
- If the cached version is stale (past its revalidation time), it is still served to the visitor
- In the background, the page is regenerated with fresh data
- The next visitor gets the newly generated page
Revalidation times by page type
| Page Type | Revalidation | Meaning | |-----------|-------------|---------| | Home page | 30 minutes | New data appears within 30 min | | Project detail | 1 hour | Project updates reflect within 1 hour | | Floorplan detail | 2 hours | Floorplan changes reflect within 2 hours | | Category pages | 1 hour | New projects in a category appear within 1 hour | | Blog posts | 1 hour | Published blog changes go live within 1 hour | | Static pages | 24 hours | About, contact pages refresh daily |
When caching causes confusion
If you update something and do not see the change immediately, caching is likely the reason. Wait for the revalidation period to pass, then refresh the page.
?revalidate=1 to the URL (admin only).Search index cache
The search index is an in-memory cache that refreshes every 30 minutes. It contains all ~6,500 projects for instant search results. New projects appear in search within 30 minutes of being added to the API.
Was this article helpful?
Related Articles
How Does Data Sync Work?
Understanding cron jobs, API data flow, and how your site stays current.
Technical FAQ
What is Red Bricks OS?
An overview of the Red Bricks OS platform, what it does, and who it is built for.
Getting Started
Setting Up Your Site
First login, admin dashboard overview, and initial configuration steps.
Getting Started