Choose the Swiss audience before choosing the language architecture.
Switzerland is not one automatic locale. The system needs an explicit audience and language matrix tied to content owners, routes, test data, support, and release approval.
Record the intended regions or audiences and whether they require English, German, French, Italian, Romansh, or another language. Assign human ownership for every published variant.
Do not launch empty translation shells
Plan canonical and hreflang only when real variants exist
Test navigation, forms, errors, and support text
MODULE 02
Locale and usability
Validate CHF display, dates, numbers, addresses, phone/contact paths, form fields, keyboard use, contrast, zoom, assistive-technology basics, devices, and browser support.
Use the minimum identity fields needed
Keep error language actionable
Do not conflate locale with legal applicability
MODULE 03
Acceptance matrix
For each audience and critical task, identify the content approver, business approver, technical evidence, test environment, release owner, and maintenance owner.
No approval by assumption
No unreviewed machine translation
One written source of truth
Measure. Decide. Implement. Verify.
Make every Switzerland release status traceable to evidence.