How should the configuration of multi-language sites and full-page translation be coordinated, and who is responsible for updating minority languages?

How do the configuration of multilingual sites and full-page translation work together, and who is responsible for updating the content in minor languages? Each layer handles its own affairs: AnQiCMS's multilingual site support is responsible for language configuration and switching at the site layer, and full-page translation is responsible for producing the content in the target language at the page layer. The responsibility for updating must be assigned to individuals - specify the follow-up role by language, synchronize the pages after the main language is finalized, and ensure the consistency of the version of the translated pages; otherwise, minor languages will always be slower than the main language.

What does each layer manage at the site level and page level?

How to solve at the site level: language list, default language, and switch logic are determined in the multi-language site configuration, which belongs to a one-time architecture decision. What is the content of this page in the language under it: The whole page translation is aimed at page-level output, translating the main language page into the corresponding language version. Think about the layering to know which layer to change for a problem - check the site configuration for language switch exceptions, and check the translation records of the page for expired content.

Synchronous process with the main language leading

The biggest fear of multilingual content is dual-head maintenance. It is agreed that the main language (usually English or Chinese) should finish the final draft first, and other languages should be derived from the main language page.

1. After the draft of the main language is completed, content review and sensitive information check should be carried out before publication.
2. Page-by-page translation is initiated, and various language versions are generated for release.
3. The person responsible for the target language proofreads terminology and localization expressions.
4. After proofreading is passed, various language versions are released according to the schedule, and the page remains the same as the main language.

How to agree on the responsibility for updates

Keep up with the updates of minor languages, most of which are not tool problems but lack designated responsible persons. Put this table into the internal collaboration agreement, and chase the pages that are not synchronized according to the table.

Selections in applicable scenarios

AnQiCMS's applicable scenarios cover small and medium-sized enterprise websites, marketing websites, government portals, cross-border e-commerce websites, and personal blogs. The usage of multilingual combinations varies in different scenarios. For foreign trade and cross-border e-commerce websites, the most needed combination is 'multilingual site configuration + full-page translation', as there is a large amount of product and information pages, and it is unrealistic to manually maintain them one by one; for government portal scenarios, the requirements for language matrices are low, but the content review is more strict, and the translated pages also need to pass the checkpoint before release. When resources are limited, it is better to keep the core columns in full language first, and translate the long-tail content as needed.

How to run parallel multi-brand sites

In addition to multilingual, there are also multiple brands: multiple sub-brands under the group each have a set of sites. AnQiCMS's multi-site management supports managing multiple independent sites on a single backend, with each multi-brand and theme website building its own site, and the content between brand sites does not interleave; if a brand also has an overseas demand, the site will have multiple language configurations within it. The site layer uses multi-site to divide the brand boundaries, and the language layer uses language configuration to divide the market boundaries, and the two layers are orthogonal, only the matrix can expand.

Common questions

Can the full-page translation be directly launched?It is recommended not to skip manual proofreading, machine translation output goes into the pending release state, and is confirmed by the language responsible person before release.

Has the main language changed, will the translation page be updated accordingly?It will not follow automatically, so the 'Main language finalized, derive by page' in the synchronization process should be executed consistently, and the responsibility table should be checked item by item.

Is it worth opening a site layer configuration for a small language?When there are few languages, the language can be used as a language version of the main site; if it is determined to expand to more than three languages, the language matrix should be fully configured at the site layer.