Astro Admin — Prebuild, Cache & Performance 2026-10-14 — Astro Admin setup

00:00:00 — Prebuild, Cache & Performance
Welcome to the Agentic Ecom Astro Admin guide to prebuild, cache & performance. We're using the Sync Comms storefront to show the current controls. We'll review the workflow with previews, without saving changes to this live store.

00:00:14 — Start with current data and layouts
Open Prebuild Pages after saving your intended presentation changes and running the required syncs. The grid lists homepage, category, product and C M S pages, with built, not-built and failed status filters. Review the current state before choosing a build action.

00:00:33 — Choose a focused build scope
Use the page-type tabs and search to narrow the list. For a small change, select the affected pages instead of automatically rebuilding the whole catalogue. Prebuild current view and Build selected have different scopes. Check the selected count and the visible filter before starting an action on your store.

00:00:53 — Review progress and failures
Built, Not Built and Failed help you inspect the outcome. A started build is not a completed build: wait for it to finish and review failures. Build Remaining is useful when the intended pages have not yet been built. We are only filtering this screen, without starting, stopping or repairing a production build.

00:01:14 — Use the appropriate cache control
Cache Management separates Global, C D N, C M S and Image caches. Use the control that matches the stale content after checking that the correct data and pages were built. A browser hard refresh is another useful check. Purging cache is an operational action, so confirm the scope before using it.

00:01:36 — Review performance settings separately
Performance has network and rendering optimisation settings. Review each option against your deployment and test the effects on real pages. Save Changes applies the selected settings; Recommended and Reset All are broad controls. We are reviewing the screen without changing its configuration. Performance options do not replace a successful build or a functioning checkout.

00:02:01 — Verify the customer result
Open View Storefront after your build finishes. Check a representative homepage, category, product and C M S page, including mobile navigation and current price and stock. If something is stale, work through saved source, sync, prebuild, server or C D N cache, then browser cache in that order.

00:02:23 — Your next steps
To put this into practice, build the intended pages, review completion and failures, check caches and real storefront journeys. Test the complete result on your own staging storefront before publishing. You can follow the written Astro Admin guides at user guides dot Agentic Ecom dot net.