One layout. Every language.
sitereal 1.0 builds sites in several languages. You design a page once, each language holds only its words, and every one of them is written as plain Astro files that build without sitereal.
Fix it once, fixed in every language.
A page has one layout and words per language. A translation holds only what differs: the text, the attributes that are words like alt text and labels, a link typed by hand, a different picture.
Each language is still written as plain files with its own words in them. Delete sitereal and every page is a readable page in its own language.
src/pages/about.astro
src/pages/de/ueber-uns.astro
src/content/posts/on-light.md
src/content/posts/on-light.de.mdChange a language’s file in your editor, or let an agent do it, and the change is read back into that language.
On the page, or in a table.
Translate mode shows the canvas in that language, with its lang and dir, and you type on the page. The Translate view puts the source, the translation and its status side by side, for pages, collections, templates, components, popups and forms.
The status is worked out from the source, never ticked by hand. Fix a typo in English and the toast offers Still fits, so no language turns outdated over it.
Nothing written in this language yet. The page shows the source’s words.
The source changed after it was translated.
Written by an AI or an agent, and not looked at by a person yet.
Written or reviewed by a person, for the source as it is now.
Any model, never over your words.
AI in the Translate view translates the rows you pick, or every row still to do. What comes back is marked as a machine’s until someone reads it, a machine never writes over a person’s words, and one undo takes a run back.
A glossary lists the terms that are never translated, like your brand, or always said one way, and a note says how the site speaks. AI runs and agents get both.
A command on this computer
Claude Code, Ollama or llm, reading the prompt and answering on its own.
An OpenAI-compatible API
OpenAI, OpenRouter, Mistral, Groq or Gemini, or Ollama and LM Studio on this computer with no key.
The Anthropic API
Claude directly. A key is the name of an environment variable, never the key itself.
Agents over MCP
An agent gets the strings with their context and glossary terms. A translation written for a source that has changed since is refused.
Content per language, where it already lives.
A content type is translated or not, and each of its fields is translated or shared. Text and links are translated. Dates, numbers, files and a select’s value are shared, so a German edit cannot change an English date.
Entry files
A translation is a complete file beside its original, on-light.de.md, with the shared values copied in.
Data files
Each language gets its own src/data/<type>.de.json, remade from the rows on every save.
Database rows
The words sit in a table beside the type’s own, made by the usual migration.
Data sources
Asked once per language: lang for WordPress with WPML or Polylang, locale for EmDash.
Addresses and search, handled.
Adding a language moves no address. The site’s own language stays at /, and the others go under their prefix.
Before or after the path
/de/services, as most sites do, or /services/de. A page can have its own address in a language, like /de/ueber-uns.
What search engines get
<html lang>, a canonical of its own, hreflang both ways with x-default, sitemap alternates and og:locale, with no setup. The build check asks for the Production URL until it is set.
A language switcher
Names, codes, flags or a flag with either, as a row or a dropdown. It follows the live languages and works without JavaScript.
A suggestion, not a redirect
Visitors are never sent away by their browser’s language. A German browser on an English page sees a bar, in German, with a link, once.
A language on its own domain
Give German example.de and publishing to Vercel, Netlify or Cloudflare uploads it as a second site from the same build.
A 404 per language
Where the host can serve one per folder: the export’s .htaccess on web hosting, and each host’s own way when you publish.
Start building the sites you’ve always wanted.
Seven days free, on your machine — and every site you build is real Astro in your own repository, yours from the first save.
