🌐 i18n - Internationalize the website

cc @piers-sinclair @wicksipedia @adamcogan @JeanThirion

1. Finish Migrating/zz'ing pages and turn off VM (Harry thinks 4 months 🤷🏻‍♂️)
2. Megamenu – Make it a separate component
3. Do a POC of the French website using AUS website content (1 month)

• Same tech as AUS (NextJS)
• A few consulting pages + Home page
• Shared component library
• Does not include Megamenu
• Links to English content (e.g. Rules)
• By default auto-translated
• Using Weglot: Weglot
• Can be overridden (better for SEO)

4. Do a POC of the China website using AUS website content (1 month), a.k.a. Chinafy
5. France + China websites – WordPress to Next.JS (6 months)
   • Use AUS website consulting content
6. Megamenu
   • Internationalize (same structure, different menu content – 2 months)
7. Adding rules and people to French and China sites
   • /rules (English)
   • /people
   • Same Megamenu
   • Maybe use ssw.com
8. 2025 | MegaSite
   • Headless CMS (e.g. Contentful – Everyone is yet to be convinced)
   • Is Tina the right CMS?

The issue provides no file or test entry point; start by reviewing the existing AUS website and its NextJS implementation. Clarify the French and China POC scope, translation approach, shared components, and content boundaries before implementation; done means a defined, working POC for the agreed scope.