New language launch checklist
This checklist must be completed before publicly activating a new language. Check each item in order.
1. Base content
- [ ] The language is created in the database
- [ ] The name and code are correct (no typos, no duplicates)
- [ ] The primary colour is defined (hexadecimal, vivid and distinctive)
- [ ] The icon/silhouette is uploaded (512×512px minimum, PNG transparency recommended)
2. Text content
- [ ] Word cards are imported via Excel
- [ ] All cards have 6 positions (1 to 6)
- [ ] No empty cells
- [ ] Themes are filled in
- [ ] Phrase cards are imported via Excel
- [ ] All cards have 4 positions (1 to 4)
- [ ] The texts for all 4 positions are correct
- [ ] The imported content has been manually verified (a few random cards)
3. Speaker and audio recordings
- [ ] The speaker is created with their name and an access code
- [ ] The speaker access code has been communicated to them
- [ ] The speaker can log in at
/speaker/login - [ ] At least 50% of audio is recorded (recommended before launch)
- [ ] A few audio recordings have been listened to to verify quality
4. Functional tests
Perform these tests from a browser in normal browsing mode (not admin).
- [ ] Access code: enter the player code from the homepage → unlock OK
- [ ] Word navigation: browse through word cards, click on a word → translation revealed
- [ ] Word audio: press 🔊 → audio plays
- [ ] Phrase navigation: browse through phrase cards, Lot 1 and Lot 2 displayed
- [ ] Phrase audio: positions 1 and 4 have playable audio
- [ ] Multiple-choice review: launch a quiz on a theme → 15/18/20 questions → final score displays
- [ ] Offline mode: trigger the download → all steps complete
- [ ] Offline test: switch to airplane mode → cards and audio still accessible
5. Activation
- [ ] The language has been set to Active status (
is_active = true) in the language list - [ ] The language appears on the public homepage
- [ ] The player access code is ready for printing in game boxes (copied with 📋)
6. Post-launch
- [ ] Statistics start appearing in the dashboard after a few uses
- [ ] Contact messages are monitored for feedback from the first players
- [ ] A reminder is set to follow up with the speaker if recordings are not completed
Summary of codes to send
| Recipient | Code | Where to find it |
|---|---|---|
| Players (game box) | Player access code | Language list → "Access code" column |
| Native speaker | Speaker access code | Language list → "Speaker code" column |