Kratonkade 17, 3024 ES, Rotterdam hallo@admix.nl, 010 27075 75
What we build, what we migrate and what's changing in the Umbraco landscape.
Updating Umbraco without going into the backoffice
Since Umbraco 14 the backoffice itself runs on an API. We had four vacancies from a Word document put on the site — with a human doing the publishing.
RAG without a vector database: AI on your own knowledge base
We tested Google's Open Knowledge Format on our own Confluence: AI answers with source references, without a vector database.
Translating from the backoffice, with AI
A multilingual site always meant exporting, sending off and importing again. We built translation into the backoffice: right-click, target language, review, apply. Including spoken audio per language.
Our site was invisible to Google
Google didn't know our tech site — not hard to find, but absent. By now: 12 of the 13 pages in the index, and the first AI assistants fetching pages live. The numbers, the approach, and the conclusions we had to retract.
Why Umbraco, and not WordPress
Multilingualism, custom content types and permissions are built into Umbraco. In WordPress they are plugins — and that's also where the lion's share of the vulnerabilities lives.
Umbraco on Linux, with zero downtime
Every site in its own Linux container: updates run alongside it with zero downtime, so staying on the current LTS is effortless.
Why LTS matters
Support, security and the cost curve: why the LTS line is the only one that really matters.
From any Umbraco version to LTS 17
Umbraco 17 is the new Long Term Support release. This is what the migration route looks like — from 8, 10 or 13.
Migrating from Umbraco 10 to 17
How we took a corporate site from an expired support window to years of runway.
