During Webhook CMS initialization, the english language file is extended by the chosen language file. If the chosen language file is missing a translation key, the english value for that key will be used.
- Fork this repo.
git clone firstname.lastname@example.org:YOUR_USERNAME/webhook-cms-i18n.git
- run default
gruntcommand and load up
http://localhost:8000. See below for options.
Add language file
If you would like to contribute a new language, add a file with an ISO 639-1 language code for a filename (ie:
fr.json for French) to the
grunt command will run a webserver for development. Open
http://localhost:8000 in your browser of choice. Choose a language to start from. Change any values you see fit. Click on the convert button to print out a JSON representation of the translation data. Copy/paste the output into your language file.
Webhook CMS uses the
translations.js file found in the
lib directory. It is created from all of the JSON files within the
grunt task runs a watch command that looks for changes to the JSON files in the
translations and compiles the
If you are not running the default
grunt task, you need to run the
grunt compile command to generate a new
translations.js file with your changes.
We try to use Semantic Versioning for webhook-cms-i18n.
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add a language in a backwards-compatible manner, and
- PATCH version when you add translation and backwards-compatible bug fixes.
Versioning can be done with the
grunt version:type command.