Skip to content
Strata

Introduction

What the template is, what ships in the box, and the principles that shape it.

Strata is a complete starting point for production websites built on Astro 7. It is the repository you clone when a new project begins, and it is also the source of the site you are reading right now. Every feature described in these docs is running on this page.

The name spells the stack: SQLite (through libSQL), Tailwind, React, Astro, Turso and Auth. Those are the layers every production site ends up needing, and here they are already in place and wired together.

What ships in the box#

Astro 7.3 with static-first output, React 19 islands animated with Motion, Tailwind CSS 4 with OKLCH design tokens and dark mode, MDX docs and blog collections, Better Auth with email and password, GitHub, Google and magic-link sign-in, Drizzle ORM with libSQL, an admin area with a contact inbox, user management and an audit log, generated Open Graph images, JSON-LD, sitemap, RSS, llms.txt, Pagefind search, a hash-based Content Security Policy, hardened response headers, Vitest, Playwright with axe, Lighthouse budgets, and adapters for Vercel, Cloudflare, Netlify and Node behind one DEPLOY_TARGET switch. The guides describe each of these in turn.

Principles#

  1. Static first. Pages are prerendered by default. Only the auth and account routes, the dashboard, the admin area, the API and form actions run on a server, and each opts in with export const prerender = false.

  2. One codebase, any host. Platform differences live in config/adapter.ts and a handful of platform config files. The application code never checks which host it runs on.

  3. Secure by default. The Content Security Policy, response headers and origin checks ship enabled. Relaxing them is a deliberate, documented change.

  4. Current dependencies. Versions are pinned and upgraded through automated pull requests that must pass the full CI matrix, including a build for every deploy target.

How to read these docs#

  • Getting started walks through installation, the project layout and configuration.
  • Guides explain each subsystem: styling, content, authentication, database, actions and forms, the admin area, privacy and data, SEO, security, testing, CI and environment variables.
  • Deploy has one page per platform with the exact settings that platform needs.
  • Reference lists configuration keys, scripts, the changelog process and frequently asked questions.

Copying the template

The fastest way to start a new project is to clone the repository and change src/site.config.ts. See Installation for the full checklist.