SUMMARY:
Fixed critical bug where footer displayed translation keys (e.g.,
"footer.about_heading") instead of actual text on all pages except homepage.
ROOT CAUSE:
i18n-simple.js only loaded page-specific JSON files (e.g., privacy.json).
Footer translations were in homepage.json, so other pages couldn't access them.
SOLUTION:
1. Created common.json for Shared Translations:
- Created locales/en/common.json (footer translations)
- Created locales/de/common.json (footer translations)
- Created locales/fr/common.json (footer translations)
2. Updated i18n-simple.js to Load Both:
- Always loads common.json (footer, shared UI elements)
- Loads page-specific JSON (privacy.json, about.json, etc.)
- Merges both (page-specific takes precedence)
IMPACT:
✓ Footer now displays correctly in all 3 languages on ALL pages
✓ Privacy page: Footer translates properly (en/de/fr)
✓ All pages: Footer translations work regardless of page-specific JSON
✓ Scalable: Easy to add more shared translations to common.json
TESTING:
- Verified locally on privacy.html (footer displays "Tractatus Framework")
- All 3 languages load correctly from common.json
- Page-specific translations still work (privacy content translates)
🤖 Generated with Claude Code (https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
6486b3e0de