You already have Claude Code. seite gives it something to work on.
The agent reads your config, your templates, and your existing content before writing anything. Output lands in the right directory with the right frontmatter. You review a diff and ship it.
No new subscription. No new UI to learn. No new commands. Just the Claude Code subscription you already have — now it can manage your whole website.
|
&&
Why seite
Most static site generators produce HTML and stop there. seite builds for three audiences at once:
- Browsers get pages with full SEO metadata, Open Graph, Twitter Cards, and JSON-LD structured data
- LLMs get
llms.txt,llms-full.txt, and a.mdcopy of every page for direct consumption - AI tools get a built-in MCP server that exposes your entire site as structured resources
All from Markdown + YAML frontmatter. No JavaScript runtime. No build dependencies. One binary does everything. 331 tests, 139 unit and 192 integration.
AI integration
Agent
seite agent spawns Claude Code with full site context — config, content inventory, templates, and available commands. No API keys, no setup. Uses your existing Claude Code subscription.
seite init generates .claude/CLAUDE.md with your site's full schema so the agent is oriented before it writes a single character. Output lands in the right directory, with the right frontmatter, following your conventions. You review a diff and ship it.
MCP server
seite mcp runs a Model Context Protocol server over stdio. Claude Code auto-starts it via .claude/settings.json, generated by seite init. Any MCP-compatible AI tool can use it.
Resources — seite://docs, seite://config, seite://content, seite://themes, seite://trust
Tools — seite_build, seite_create_content, seite_search, seite_apply_theme, seite_lookup_docs
This means your AI tool doesn't just have read access to your site — it has a structured interface to build, search, and modify it.
LLM discovery
Every build generates llms.txt (summary) and llms-full.txt (complete markdown) for LLM indexing, plus a .md copy of every page. Multilingual sites get per-language versions. Traditional SEO and GEO handled in one pipeline, automatically.
Features
- 6 bundled themes — default, minimal, dark, docs, brutalist, bento — or generate a custom one with
seite theme create "coral brutalist with lime accents" - 6 collection presets — posts, docs, pages, changelog, roadmap, and trust center
- Multi-language — filename-based i18n with per-language URLs, RSS feeds, sitemaps, search indexes, and hreflang tags
- Image pipeline — auto-resize, WebP conversion, srcset/
<picture>elements, lazy loading - Deploy anywhere — GitHub Pages, Cloudflare Pages, Netlify with guided setup, pre-flight checks, and
--dry-run - Analytics — Google Analytics, GTM, Plausible, Fathom, Umami with optional cookie consent banner
- Shortcodes —
youtube,vimeo,gist,callout,figurebuilt-in, plus user-defined templates - Multi-site workspaces — manage multiple sites from one directory with unified dev server
- Self-update —
seite self-updatefetches the latest release with SHA256 checksum verification
Install
macOS / Linux:
|
Windows (PowerShell):
irm https://seite.sh/install.ps1 | iex
From source (requires Rust):
Pin a specific version:
VERSION=v0.1.0 |
Quickstart
Open http://localhost:3000. Edit content in content/, templates in templates/. Live reload on every change.
# Create content
# Deploy
Build output
seite build runs a 13-step pipeline and produces:
dist/
├── index.html
├── posts/
│ ├── hello-world.html # HTML for browsers
│ └── hello-world.md # Markdown for LLMs
├── docs/
│ └── getting-started.html
├── feed.xml
├── sitemap.xml
├── search-index.json
├── robots.txt
├── llms.txt
├── llms-full.txt
├── 404.html
└── static/
Every HTML page includes canonical URLs, Open Graph tags, Twitter Cards, JSON-LD structured data, and a link to its markdown alternate.
Collections
| Preset | Dated | RSS | Nested | Use case |
|---|---|---|---|---|
| posts | ✓ | ✓ | — | Blog posts, articles |
| docs | — | — | ✓ | Documentation with sidebar navigation |
| pages | — | — | — | Standalone pages (About, Contact) |
| changelog | ✓ | ✓ | — | Release notes with colored tag badges |
| roadmap | — | — | — | Public roadmap with status tracking |
| trust | — | — | ✓ | Compliance hub (SOC 2, ISO 27001, GDPR) |
Themes
Six themes ship with the binary — no downloads, no CDNs:
| Theme | Description |
|---|---|
| default | Clean centered column, system fonts, blue links |
| minimal | Georgia serif, literary feel, generous whitespace |
| dark | True black #0a0a0a, violet accents, visible focus rings |
| docs | Fixed sidebar with auto-scrolling nav, GitHub-style |
| brutalist | Cream background, thick black borders, hard shadows, yellow accents |
| bento | CSS grid cards, rounded corners, mixed sizes, soft shadows |
Multi-language
Filename-based translations. Single-language sites need no config.
content/posts/
├── hello-world.md → /posts/hello-world
├── hello-world.es.md → /es/posts/hello-world
└── hello-world.fr.md → /fr/posts/hello-world
[]
= "Mi Sitio"
[]
= "Mon Site"
Configuration
# seite.toml — minimal
[]
= "My Site"
= "https://example.com"
[[]]
= "posts"
[]
= "My Site"
= "A site built with seite"
= "https://example.com"
= "en"
= "Your Name"
[[]]
= "posts"
# name = "docs" | "pages" | "changelog" | "roadmap" | "trust"
# paginate = 10
[]
= "dist"
= "data"
= true
= true
[]
= "github-pages" # or "cloudflare" or "netlify"
= true
[]
= [480, 800, 1200]
= 80
= true
= true
[]
= "plausible" # or "google", "gtm", "fathom", "umami"
= "example.com"
= false
[]
= "Mi Sitio"
[]
= "Acme Corp"
= ["soc2", "iso27001"]
Data files
Drop YAML, JSON, or TOML in data/ and access in any template:
# data/nav.yaml
- title: Blog
url: /posts
- title: Docs
url: /docs
Available as {{ data.nav }} in all templates.
Workspaces
Deployment
[]
= "cloudflare" # or "github-pages" or "netlify"
seite init auto-generates the CI workflow for your chosen target.
Documentation
Full docs at seite.sh/docs
- Getting Started
- Configuration
- Collections
- Templates
- Shortcodes
- Multi-language
- Deployment
- CLI Reference
- Trust Center
Contributing
seite is early and issues, PRs, and feedback are genuinely welcome. Especially useful:
- Bug reports with a repro case (even a minimal
seite.toml+ content file) - New theme ideas — open an issue first to align on direction before building
- Docs improvements — if something confused you, it'll confuse others
- Real-world usage — if you build something with seite, share it
Open an issue before starting a large PR — saves everyone time.