Cloudflare-Native Deployment for Astro

Astro can render a website in several ways, and Cloudflare can run almost all of them. AstroWEBTheme picks a sensible default and documents the tradeoffs instead of leaving the decision to trial and error.

Static, server-rendered, or hybrid

A purely static Astro site deploys cleanly to Cloudflare as prebuilt assets. A site that needs personalization, authentication, or live content benefits from server rendering through the @astrojs/cloudflare adapter instead. AstroWEBTheme supports both, plus a hybrid mode where most pages stay static and specific routes render on request — so a marketing site and a lightweight application can share one deployment.

D1 for content that changes often

Cloudflare D1 backs the theme’s live content model: posts, pages, and other entries can be stored as database rows instead of files, with the same layouts, feeds, and metadata as static content. This matters for collections that change frequently or need an editing workflow beyond committing to Git.

R2 for public and private media

Media assets — images, documents, downloads — are stored in Cloudflare R2, split between a public bucket for assets served to visitors and a private bucket for gated or access-controlled files such as publication downloads.

KV for sessions and short-lived tokens

Where a project needs authentication, password resets, or download tokens, Cloudflare KV handles short-lived state without adding a separate service to operate.

One generated configuration

wrangler.jsonc and .dev.vars are generated from the theme’s own config rather than edited by hand, which keeps bindings (D1, R2, KV) consistent between local development and the deployed Worker. The Cloudflare deployment checklist walks through what to verify before going live.

Prefer to have the Cloudflare account, domain, and bindings configured for you? NViewsWEB handles Astro + Cloudflare deployment as a standalone engagement.