Performance & Caching

Who is this for? Developers tuning a Capell site for speed, building cache-aware integrations, or wiring CDN invalidation.

Capell ships several layered performance features. Pick the guide for the layer you’re working with:

Layer	Guide	Use when
Page-level HTTP cache	Page cache architecture	Tuning the static-HTML cache
Model URL cache index	Model URL cache	Understanding URL-to-model cache dependencies
HTTP conditional responses	ETag & conditional responses	Reducing bandwidth on unchanged pages
In-template fragments	Fragment caching	Caching expensive Blade partials
Asset delivery	Critical asset optimization	Tuning render-blocking CSS / preloads
Cache busting	Cache invalidation	Wiring model changes to cache flushes
Page rendering	Lazy page hydration	Avoiding eager loads on cold cache hits
HTML output size	`capell-app/frontend`	Conservatively minifying rendered HTML and page-cache writes

Frontend Authoring uses the model URL cache to find every cached URL touched by an edited record. The editor itself is never baked into cached HTML; admin-only edit controls are added later by the beacon.