Folder structure and stubs for i18n of the static website.

[mikeal]

This is so that we have something to point the newly formed translation teams at so they can start translating the website.

Yes, we'll have to migrate these after the new tooling is done but that can be done by the translation communities themselves once we have the tooling in place and documented. As it stands the tooling is blocking us from giving broader access to io.js so we should just move forward.

[fengmk2]

@mikeal merge this? i18n/cn will be ready soon.

[mikeal]

@fengmk2 I need at least one other +1 from the website WG :)

[mikeal]

@snostorm @Fishrock123 @indexzero @therebelrobot can I get a quick +1 :)

[Fishrock123]

Shouldn't it be /public/<lang>/content?

otherwise you'll have to go to iojs.org/i18n/<lang>/...

We also need to do some nginx stuff to redirect, I can take a look tomorrow.

[therebelrobot]

The build process is making public/<lang> folders, I thought that's what we were going with. If that needs to change let me know.

[snostorm]

Ya, also confused by this. The i18n prefix should be removed as public should reflect the post-build process output until it is merged.

[therebelrobot]

The pull request for the new build/i18n structure is in #119, so this may be a bit preemptive.

[therebelrobot]

I did, however add the new languages to the structure.

[mikeal]

Closing this since @therebelrobot is about to mere proper tooling :)