Skip to content
astro-template
MITGet started
Astro 7 · Cloudflare Workers · pnpm monorepo

An Astro monorepo,
already set up

A starter with a landing page and a blog on Astro 7, Tailwind v4 and Svelte 5. Linting, E2E tests, build audit, CSP and deployment to Cloudflare Workers are configured. MIT-licensed.

Template on GitHubStarter demo
Astro
7.3.2
Tailwind CSS
4.3.3
Svelte
5.57.0
Node.js
≥ 22.12
Stack
  • Astro 7
  • Vite 8 · Rolldown
  • Tailwind v4
  • Svelte 5
  • TypeScript 6
  • Zod v4
  • Biome 2
  • Playwright
  • axe-core
  • pnpm 11
  • Cloudflare Workers
  • MIT
01 — Overview

The setup every project otherwise repeats.

Astro ships static HTML and loads JavaScript only for islands you add explicitly. The template adds the toolchain that otherwise gets rebuilt in every project: linting and formatting, tests, audits, security headers, multiple languages and deployment. A new app is a folder under apps/ that shares tokens and components from shared/.

github.com/casoon/astro-v7-template →
  1. 01Two apps — starter with a landing page and contact form, blog with MDX and RSS
  2. 02Shared base — tokens, components, layouts and utilities in shared/
  3. 03Central versions — one pnpm catalog for every app
  4. 04Tracks Astro 7 — the template is updated with Astro 7 releases
02 — Get started

Clone, install, run.

  1. 1Clone

    Get the repository

    Requires Node.js 22.12.0 or later and pnpm 11 or later.

    git clone https://github.com/casoon/astro-v7-template.git
  2. 2Install

    Fetch dependencies

    One install for all apps; versions come from the catalog.

    pnpm install
  3. 3Develop

    Start the dev server

    Starter on port 4321, blog on port 4322.

    pnpm dev · pnpm dev:blog
  4. 4Deploy

    Ship to Cloudflare

    Builds the app and runs wrangler deploy.

    pnpm deploy:starter
03 — Features

Configured, not just installed.

Tailwind v4

CSS-first configuration through the Vite plugin, OKLCH colours, dark mode from the system setting plus a toggle.

Svelte 5 runes

Reactive islands with $state and $derived. Pages without an island ship no framework JavaScript.

i18n (en/de)

Astro i18n routing: English without a prefix, German under /de/, hreflang in the sitemap.

Security

Astro’s built-in Content Security Policy with SHA-256 hashes, plus checkOrigin against CSRF.

Astro Actions

A contact form with server-side handling and Zod validation.

OG images

Generated at build time with Satori and resvg, per page and language.

Playwright + axe-core

15 spec files across both apps: navigation, SEO, i18n, form, theme and accessibility scans.

Code analysis

fallow finds unused files, exports and dependencies, complexity hotspots and duplication.

Blog app

MDX with content collections, a table of contents with scrollspy, a reading progress bar and an RSS feed at /rss.xml.

04 — Astro 7

What Astro 7 changes in the template.

CriterionAstro 7Astro 6
BundlerVite 8 + RolldownVite 7 + Rollup
.astro compilerRust, rejects unclosed tagsGo
MarkdownSätteri, GFM and heading IDs built inremark/rehype with plugins
compressHTML (default)'jsx'true
@astrojs/cloudflarev14, workerd in every stagev13
src/fetch.tsreserved for advanced routingfree to use

As of September 2026, according to the template’s README. With compressHTML: 'jsx', whitespace between inline elements can disappear – add {" "} where needed.

05 — Structure

One workspace, clearly split.

Project structuretree
astro-v7-template/
├── apps/
│   ├── starter/          # landing page, contact form, i18n
│   └── blog/             # MDX blog, RSS, i18n
├── shared/               # tokens, components, layouts, SEO
├── integrations/         # custom integrations
├── e2e/
│   ├── starter/          # Playwright tests
│   └── blog/
├── .github/workflows/    # CI pipeline
├── biome.json
├── playwright.config.ts
└── pnpm-workspace.yaml   # workspace + catalog
pnpm-workspace.yamlCatalog
# pnpm-workspace.yaml
catalog:
  astro: ^7.3.2
  "@astrojs/cloudflare": ^14.3.1
  "@astrojs/svelte": ^9.0.1
  tailwindcss: ^4.3.3
  svelte: ^5.57.0
  typescript: ^6.0.3
  zod: ^4.5.4
  "@biomejs/biome": ^2.5.12
  "@casoon/astro-post-audit": ^0.6.0
  "@casoon/astro-structured-data": ^2.0.1
06 — Ecosystem

Six CASOON packages, already wired up.

@casoon/astro-post-audit

Build audit

Checks SEO, links, HTML and accessibility rules after every build. Only real errors fail the build.

0.6.0
@casoon/astro-site-files

Site files

Generates robots.txt, sitemap.xml with hreflang, llms.txt, security.txt and humans.txt.

0.5.0
@casoon/astro-structured-data

JSON-LD

Typed schema components; with generateMeta they also produce Open Graph and Twitter tags.

2.0.1
@casoon/astro-speed-measure

Build metrics

Measures build time per integration, Vite plugin and page.

0.4.0
@casoon/astro-webvitals

Web Vitals

Measures LCP, CLS and INP in the browser. In production, 10 % of sessions report to a typed endpoint.

0.4.8
@casoon/nosecrets

Secret scanning

A pre-commit hook and a workspace scan that keep API keys and tokens out of the repository.

0.3.7
07 — Limits

Worth knowing up front.

A template makes decisions for you. These ones are deliberate.

Cloudflare by default

Other platforms need three changes per app: swap the adapter, enable Sharp as the image service, delete wrangler.toml.

TypeScript stays on 6

astro check relies on an API that TypeScript 7 does not expose yet, so the version is pinned to ^6.0.3.

Web Vitals without storage

The endpoint validates the metrics and answers with 204. Where the data goes is up to your project.

English as the default locale

English lives at the root without a prefix, German under /de/. Adjust the i18n config if you need it the other way round.

08 — A good fit for
  • Marketing websites
  • Blogs and content sites
  • Landing pages
  • Agency starters
  • Multi-app monorepos
  • Cloudflare projects
09 — FAQ

Frequently asked questions.

Why a monorepo instead of a single project?

Several apps – say a website, a blog and landing pages – share design tokens, components and tooling while staying individually deployable. A new app is a folder under apps/ that imports from shared/.

Do I have to use Cloudflare?

No. The template is preconfigured for Cloudflare Workers. For Node.js, Vercel or Netlify you swap the adapter, enable Sharp as the image service and remove wrangler.toml.

What changes with Astro 7?

Vite 8 with Rolldown as the bundler, a Rust compiler for .astro files that rejects unclosed HTML tags, and Sätteri as the markdown processor with GFM built in. compressHTML is set to jsx, so whitespace between inline elements can disappear.

How does my project stay up to date?

The template is a starting point, not a package: once cloned, the code belongs to your project. Versions live centrally in the pnpm catalog, and a Renovate configuration is included.

Is the template prepared for coding agents?

Yes. CLAUDE.md holds the project rules, .claude/mcp.json an MCP configuration, and the .ai/ folder prompts and knowledge files. Astro 7 also adds astro dev --background for agents and CI.

Which licence applies?

MIT. You may use it commercially, modify it and redistribute it.

10 — From the ecosystem

Pairs well with.

astro-post-audit

Build-time audit for Astro: SEO, links and accessibility

astro-structured-data

Typed Schema.org components for Astro

astro-site-files

All site files for Astro from one configuration

Start with a ready-made toolchain.

Astro 7, Tailwind v4, Svelte 5, tests and audits – MIT-licensed and ready for Cloudflare Workers.

Template on GitHubView the starter demo