Add i18n as a step in the process

Title says it all, there is an i18n example in the documentation, though I think i18next would be preferable.

The documentation example, however, is naïve, it places the locales in one folder, which is okay for a framework default and as a starting point. As a developer with some localization experience I prefer to make each class/plugin/component etc. have their data, configuration, locales, etc. in the same place for maintenance and of course for creating parts that do one thing only.

I guess it's up to me to tool this?