implement multi-language support pattern across backend and frontend
New feature shipped to Inkwelly— India's most actively developed school management software. This change is in production at real Indian schools today, not on a roadmap.
- Introduced a comprehensive multi-language support pattern for handling user-entered content.
- Defined rules for translatable and non-translatable fields, including JSONB column structure.
- Established a fixed list of supported languages and their corresponding ISO codes.
- Created shared helpers and DTO patterns for consistent handling of I18n fields in NestJS.
- Updated API contracts to include optional I18n fields in request and response shapes.
- Implemented frontend localization using next-intl, including helper functions for localized value retrieval.
- Added detailed checklists for migrating existing modules and creating new ones with multi-language support.
- Documented anti-patterns to avoid and provided a reference implementation in the Student module.
This isn't a roadmap. It's already running in your competitor's school.
Every update on the Inkwelly changelog is in production at real Indian schools today. If you're tired of ERP vendors who promise features for “next quarter”, let's talk. We run a 90-day paid pilot with a pro-rata refund and full data export.