API localization: open questions

[stringparser]

Previously handled in nodejs/nodejs.org#211. Echoing here.

Open questions were:

• when we can start?
• what the structure of the folder should be?
• how it would be merged into main website?

Feedback: some localization groups have started the translation of API docs (iosj-ru, iojs-es). The documentation wasn't migrated over the documentation to the website group. Tooling missing at the moment.

[chrisdickinson]

what the structure of the folder should be?

Ideally it would echo the folder structure of this repo.

when we can start?
how it would be merged into main website?

We don't have a Makefile (or really any way to build the docs that we're writing) at the moment. Once we have that we should be able to kick off i18n in earnest.

[bnb]

Pinging @mikeal on this one - he is the best person to talk to about getting the i18n going like it did with the iojs/website.

[chrisdickinson]

My current line of thought is to make the tools easy to work with, and the directory structure bog-standard, then to allow for the same sort of fork-it-and-run-with-it strategy as the other i18n efforts.

[watilde]

@nodejs/nodejs-ja also started having a discussion about this. Like the GNU gettext way, it would be nice if we have the translated API docs as a separated repo and require them from core/website, but we still couldn't integrate it into them with something tools since we don't have the way yet.

[Trott]

Closing as this repository is dormant and likely to be archived soon. If this is still an issue, feel free to open it as an issue on the main node repository.