01
Draft in every language
A language becomes required only once it is switched on for that piece.
Multilingual publishing, static front end
Content / CMS platforms
A site in several languages turns every content change into a developer ticket, and an editor can’t see what’s about to go live until it is.
Named by what it does, not who it was for. The screens below are illustrations we drew — never customer software.
Our solution
Each piece of content holds every language together, with a switch per language, and publishing writes the page straight to the site, with no deploy and no database behind it.
How it works
4 steps, start to finish.
02
Preview it
The real page renders at a temporary address before it is published.
03
Publish without a deploy
A timestamped copy of the old version is kept, then the new page is written to the live site.
04
Quick updates
Short, frequent items use a simpler list per language, with the same draft-and-publish rhythm.
Contact
Does this look like your problem?
Email what you are trying to fix. We will say whether a product covers it, whether it needs a build, or whether we should step aside.