🌍 Localization Guide — Translate FlowInquiry
FlowInquiry supports internationalization using next-intl
No coding skills needed — just basic JSON editing and language knowledge.
📁 Folder Structure
All translation files live in:
Each file contains key-value pairs:
{
"locale_switcher": {
"fr": "French",
"en": "English",
"label": "EN"
},
"common": {
"buttons": {
"create": "Create",
"creating": "Creating ...",
"clear": "Clear",
"submit": "Submit",
"submitting": "Submitting ...",
"cancel": "Cancel",
"previous": "Previous",
...
}
}
}
You only need to update the values — the keys must remain unchanged.
🛠️ How to Contribute a Translation
- Fork and Clone the Repository
git clone git@github.com:<your-username>/flowinquiry.git
cd flowinquiry
- Add or Update a Language File
To improve an existing language (e.g., fr.json):
Open the file in
apps/frontend/messages/
and update any missing or incorrect translations.
To add a new language: Copy the English file and rename it with your language code:
cp apps/frontend/messages/en.json apps/frontend/messages/es.json
Then update the values in es.json (Spanish in this example).
- Submit a Pull Request Once you’re done:
-
Commit your .json file and any locale additions
-
Push your branch
-
Open a pull request on GitHub
Please include:
-
Your locale code (e.g., es)
-
What you translated or reviewed
-
Any context you’d like to share
🙏 Tips
-
Focus on quality, natural phrasing over literal translations.
-
You can leave values in English if you’re unsure — others can improve them later.
-
Don’t worry about perfection — every contribution helps!