Add localization to website about harpjs.com

[kennethormandy]

I think that sounds good, but maybe it should be at harpjs.com/docs/es and harpjs.com/docs/pt, etc? To me, it makes sense to start with the documentation since that’s the part that benefits most from the translation. The landing page is changing right now, and (presumably) there blog posts and stuff won’t get translated.

Also, if you haven’t already started, the current working branch is ko-refresh, the docs folder is here https://github.com/harp/harpjs.com/tree/ko-refresh/public/docs Almost everything is the same documentation-wise right now, but that will be getting merged into master soon.

[brendaw]

I started to translate only locally. Sooner will post the fork with your advices.

We, as translators, could really start with the docs section, but I think is better to translate the other parts from the site too (only the blog section would not get translated), especially the landing page section. This is the part which the people arrive in the first place, so it is interesting to be received in their local language.

I think it is better to structure early the site to receive the whole translation, even if it begin with the docs.

The order that sounds ideal to be done:

• Define this structure harpjs.com/pt/content as a local to the translations
• Start to translate the site always with the docs
• Then translate these other parts, just to complete the whole translation

I think this is a good guide to this and further translations.

[kennethormandy]

Okay, well just as a heads up the non-docs pages are going to be changing in that branch (we are currently writing new content). So the index page especially isn’t worth doing right now. The docs, especially the preprocessors section, is the most stable thing to start with I think.

[a-c-m]

Is there a harpjs best practice or module or tutorial to help with internationalisation strategy/structure ?