What Astro 6 Changed for Pagesmith Sites
Update, August 2026: New Pagesmith sites now use Astro 7. This post records the move to Astro 6 that we made in May 2026.
Astro 6 improved its content layer, Cloudflare support, and security controls. These were the main changes relevant to Pagesmith sites at the time.
Live Content Collections: live data, rendered into the page
Live Content Collections changed how an Astro site could handle data stored elsewhere.
Previously, external content was often included during a build or fetched in the visitor’s browser. Build-time content could become stale between publishes. Browser-side fetching could add a loading state and require JavaScript before the content appeared.
Live Content Collections let an on-demand page fetch current data and render it into the response HTML. The main content does not have to wait for a browser-side fetch.
This is useful for sites built around external data. A live collection can support sources such as:
- Shopify: products, prices, and stock pulled into an on-demand page.
- Notion: content that can change without a full site rebuild.
- Linear: roadmap, changelog, or status data rendered from a workspace.
Catalogs, listings, schedules, and feeds are all possible uses. Each integration still needs its own data source, cache policy, error handling, and page design.
Rendering and development improvements
Astro 6 updated its development server and rendering pipeline. The practical result for Pagesmith was a closer match between local development and the production runtime.
Actual page speed still depends on the site design, images, scripts, integrations, and network conditions. We test those factors separately instead of treating a framework upgrade as a guaranteed performance gain.
Improved Cloudflare Workers support
Pagesmith sites run on Cloudflare’s network. Astro 6 improved the Cloudflare adapter and moved local development to Cloudflare’s workerd runtime. This made development behavior closer to production.
This reduced framework-specific setup in the deployment path and made runtime differences easier to catch before publishing.
Built-in Content Security Policy support
Astro 6 added stable support for configuring a Content Security Policy. CSP can restrict which scripts and other resources a browser is allowed to load. It must be enabled and configured for the site; the framework upgrade alone does not apply a complete policy automatically.
Why we adopted it
Astro 6 matched several parts of the Pagesmith architecture:
- Pagesmith deploys sites to Cloudflare, which Astro 6 supported more directly.
- Live Content Collections created a clearer path for pages that depend on external data.
- Built-in CSP controls reduced the need for custom framework code.
We adopted the release after testing it against the build and publishing workflow.
What you need to do
No action was required when Astro 6 launched. New Pagesmith sites now use Astro 7. Existing sites can receive the current framework version automatically when they are opened in the editor.
For current framework and publishing changes, see the Pagesmith changelog.
