How to Set Up Multi-Language/Version Knowledge Bases in Emovart – Emovart Docs

One help center is rarely enough once your audience grows. Emovart's versions feature lets a single project carry multiple parallel knowledge bases: an English and a German one, a "v1" and a "v2", or any mix you need. Each version is backed by its own Notion page tree, gets its own address, shares your branding — and visitors hop between them with a switcher in the header.

Why run multiple versions?

A few situations where versions earn their keep:

Languages. Serve English at docs.example.com and German at docs-de.example.com, each fully translated — articles and interface strings alike.
Product versions. Keep legacy documentation online for v1 users while v2 becomes the default.
Audiences or editions. A public knowledge base plus a partner or enterprise edition with extra articles.

Because every version has its own Notion root page, different teams can write and translate independently without stepping on each other's work.

Watch the video tutorial

Prefer watching over reading? This walkthrough covers the whole setup end to end:

1. Open the version settings

Head to Settings → Help Centers on emovart.studio, select your site, and open the Versions tab. You'll see your current site listed there as the default version.

💡

Your existing site automatically becomes the default version — nothing about its URL, content, or settings changes when you start adding more versions next to it.

2. Create a new version

Click Add version. Emovart offers two paths from here:

Option 1: Quick language setup

Pick a language from the list — German, French, Spanish, and so on. Emovart pre-fills the version label, the language code used for hreflang tags, and a suggested subdomain like docs-de. This is the fastest route for translations.

Option 2: Custom version setup

Name the version anything you like — "v2.0", "Enterprise", "Beta" — and choose the label that should appear in the switcher. Use this for product versions and special editions rather than languages.

3. Duplicate your Notion template

Each version needs its own Notion root page, and the easiest starting point is a copy of what you already have:

In Notion, open your current root page and choose Duplicate.
Rename the copy so the two are easy to tell apart — for example "Help Center — DE".
Translate or adapt the content. Keep the collection structure the same where you can; parallel structures are far easier to maintain.

4. Connect the new version to Emovart

Back in the console, the new version asks for its content source. Connect it exactly the way you connected your first site: click Browse my Notion pages and pick the duplicated root page, or paste the page link directly. Emovart imports collections, sub collections, and articles from that tree only — versions never mix content with each other.

5. Publish the new version

Once the first sync finishes, review the imported structure and hit Publish. The version goes live at its own address — a sibling subdomain of your custom domain if you use one (like docs-de.example.com), or its own *.emovart.studio address otherwise.

💡

Each version syncs on its own schedule. After a big editing session in Notion, press Resync on that specific version instead of waiting for the automatic pass.

6. Customize and edit version settings

Every version can be tuned individually: open its Edit menu to change the label, language code, domain, and Notion source.

💡

Pair each language version with translated interface strings. The overrides described in Overriding default words on your site are stored per version, so your German visitors can see "War das hilfreich?" instead of the English default.

⚠️

Two settings deserve extra care: changing a version's Notion root page replaces its entire content on the next sync, and deleting a version takes its URLs offline immediately. Double-check which version you're editing before saving either change.

7. Test everything, then go live

Before announcing anything, click through each version like a visitor would. The header switcher should list every published version, search should only return results from the version you're browsing, and article links should keep you inside the current version.

Both layouts support versions out of the box — the switcher sits next to the search bar on the Help Center layout and in the top navigation bar on the Documentation layout.

Emovart Widget: switching versions

The embedded widget can point at any version you've published. Set the widget's data-site attribute to the slug of the version you want to serve — your German app build ships the widget with the German version's slug, your English build ships the default. That way, in-app help always opens in the language (or product version) that matches the surrounding product. If you load the widget dynamically, you can even pick the slug at runtime based on the signed-in user's locale.