Shipping Multi-Language, Multi-Site

One codebase, several languages, several national subsidiaries with slightly different content: a request that sounds like a translation problem and is usually, underneath, a content architecture problem. Getting the structure right (how a translated page relates to its original, who can edit what) matters more than the translation mechanism itself.

• TYPO3: Multilingual Content Trees Done Properly covers a content structure built for this from the start.
• WordPress: Multisite and WPML covers two different WordPress answers to two different versions of this problem.
• Symfony: The Translation Component covers translating an application’s own interface, not its content.