Build a Multilingual Site

Multilingual projects become expensive when the language strategy is delayed. Decide the URL structure, tree layout, and editorial ownership model before translated content starts to grow.

Recipe

1. decide whether each language gets its own tree branch
2. choose the package that will own the language workflow
3. define how translated pages relate to each other
4. make navigation and URL rules explicit before editors create large amounts of content

For current projects, start with modern language tooling such as sLang and sMultisite. Bring older patterns in only when the migration path requires them.