Install a Webhaven site and you get English as the main language with Dutch sitting right next to it. English lives at /about, Dutch at /nl/about, with a language switcher in the header and a URL structure search engines are happy with. Nothing to configure, nothing to remember.
Everything on your site is translatable: pages, blog posts, categories, media, menu links, even the site settings.
Not "translatable once you go and tick the boxes", but translatable already.
Dutch arrives pre-translated
This is the part I am quietly proud of. Dutch is not an empty language waiting for you to fill it. The interface is translated. The cookie banner and every service inside it is translated. Both forms are translated, labels and confirmation messages. So are the site slogan, the maintenance message, and the small stuff on the blog overview like the load more button.
Translations for Drupal core and contrib come down from Drupal's own translation server, checked weekly, so your admin does not slowly drift back into English as you add modules.
And Dutch ships switched off
Deliberately. Dutch is configured and translated, but invisible to visitors until you say so. No entry in the switcher, no hreflang tag, no sitemap alternate. Because there is nothing sadder than a Dutch interface wrapped around English content, announced to Google.
Translate your pages, then flip one switch under Configuration, Regional and language. That is the whole launch procedure.
Canvas pages translate
Multilingual usually falls apart with visual page builders. You translate a page, end up with two entirely separate layouts, and they start drifting apart immediately. Fix the spacing on the English version and the Dutch one keeps the old spacing forever.
Webhaven does not work that way. A translated Canvas page shares its structure with the original and translates only the words inside it. Your translator swaps text, not components. Change the layout later and that change lands in every language automatically. One page, one design, many languages.
Images follow the same principle. The file is shared across languages, the alt and title text translate. No re-uploading the same photo in five places.
Want a third language?
French, German, Spanish, whatever the project needs. Add the language and Drupal fetches the interface translations for you. Webhaven's own wording, the cookie banner and the forms, gets translated once and then it is done.
A content type you add later is yours to switch on: tick it under /admin/config/regional/content-language, and the Translate tab appears on it straight away.
A site template, not a starting point
The difference between a site template and a starter kit is what you still have to add afterwards. Webhaven's answer to that keeps getting shorter. SEO is configured, accessibility is built in, Drupal 12 is covered when it is launched, and multilingual now sits in the foundations too, page builder included.
Ready to turn it on? The multilingual documentation walks through enabling Dutch, translating your first page, and adding a third language.
Now go build something in multiple languages.
