TwoDo CMS⁴: a new generation of website management

A company’s phone number rarely changes. When it does, you find out how many places on the website it was typed by hand: the footer, the contact page, each branch, and the English version nobody remembered. Small chores like that are the brief for CMS4.

We started building the new generation of TwoDo CMS in July 2026. We first wrote about our own CMS in 2020, but CMS4 is a fresh build, shaped by the questions client websites have asked us since. In November it is in beta use: P+P has run on it since 1 November, and we are preparing this TwoDo website on it too.

Changes start in a workspace

Edits are not made in front of visitors. You prepare copy, pages and language versions in a workspace, check them in preview and only then publish. Publishing creates a new version of the whole website at once, so visitors only ever see the finished result.

A seasonal offer is a typical case: the main page, several landing pages and their translations are prepared as one piece and go live together. Editing and publishing can belong to different people, and content history lets you look up previous versions.

Content as data, design as components

A CMS4 page is assembled from components. We design them around each brand and write them in TypeScript, HTML and SCSS; the system compiles them and stores them as finished building blocks. Editors work with fields rather than code: heading, text, image, link. The component holds the layout; the content stays content.

Anything that repeats does not need several copies. A shared contact record can feed the footer and the contact sections, so you fix that phone number once and check the change in page and language previews. Services, team members and references work the same way: one reference can appear on the homepage, in the portfolio and beside a particular service.

Every language with its own URL

Each language version can have its own copy, page URL and metadata while staying connected to the same page in the other languages. The CMS handles canonical URLs, language alternates, a sitemap and structured data. That is how this website appears in four languages from one system.

AI with the permissions you grant

Through MCP, an AI agent can work with actual pages, content and components, not with text that someone then copies between tools by hand. The agent has only the permissions you give it. Editing copy, changing components and publishing do not have to belong to the same role.

We do not see AI as a replacement for accountability. The brief, checking the result and a deliberate decision to publish stay with people.

Review prepared changes as you would a colleague’s draft: facts, tone, translation and how it looks on the page.

How we start a new website

A new website starts with its content. Before we design the structure, we need answers to four questions:

1. Who will edit the website, and who decides what gets published?

2. How many languages will it have, and which texts differ between them?

3. What repeats across the site: contacts, services, team, references?

4. Which other systems does it need to connect to?

The answers become a content model and a deployment plan. For what CMS4 does today, see the TwoDo CMS page.