Localization

Localization is a feature that allows you to support i18n on your spaces.

By default, every space has the English language, which means that all the labels that are displayed on the public documentation to users will be set in English. If the space is in a different language, we are making sure to translate all Archbee static labels to match and provide full i18n support.

We consider that a language translation is just another version of a space, so the process of creating a space that supports a different language than English is similar to Version Links .

1. Click on the gear icon ⚙️ for settings, then go to the Version Links tab, under SITE LINKS section
2. Enable the version link feature for that space
3. Start building the Version Links:
   1. Select the space you want to Clone from. This will let you select the current space or children of this space.
   2. Add a label (e.g., French, English, German, etc.)
   3. Select the space language in conjunction with the label name.
   4. Click Create Version
4. Repeat the add Version Link process, until you add create your desired structure
5. Exit the Space Settings window, and publish the space, and they'll be propagated.

We automatically detect if the Version Links are meant to translate a space or to define multiple product versions.

For the moment we are supporting (English, French, German, Italian, Spanish, and Russian) and this configuration can be done only in the Enterprise plan.

Once published you will be able to see the changes in public spaces. The versions will be displayed based on the context. If the Space does contain a Space Link and also has multiple versions, it will be displayed in the Space Link Tab:

Otherwise, it will appear above our search bar:

This solution provides great flexibility based on your organization needs. We can create more complex setups like wireing Spaces, with version that need translation or vice-versa.

For Example we would have Employee Handbook and User Guide that are linked together.

On Employee Handbook we need to translate the space in multiple Languages, like English, French, Italian. And also, on Italian, you might need different versions of that product, so you can generate multiple versions of the product, for a specific language.

Same thing goes the other way around, when you would start by first translating the spaces, User Guide FR, User Guide DE, and then realizing that you need to add multiple product versions to that space and you might also have different versions based on country market.