What approach should I follow to translate the doc?

[nestjs]

What approach should I follow to translate the doc?

[linsolas]

Hello,

I would be happy to participate to the translation too (in french also, @quen2404).
Any news regarding a support of i18n / move to markdown?

[kamilmysliwiec]

Hi @cserron,
In the best case, we should try to use https://angular.io/guide/i18n, but it needs some additional effort. I can take care about it, but in the meantime maybe let's just keep translating docs in the independent project :)

[quen2404]

Hi @kamilmysliwiec, is there any news about this ? I want to translate the documentation in my native language (french).

[mazyvan]

I can help with Spanish 👍

[ShGKme]

As most of content is in markdown, i18n seems to be not the best solution. What about just splitting markdown doc files into language subdirectories like content/en/cli, content/sp/cli, content/ru/cli and then choose content according to subdomain | path?

[ShGKme]

If we create a translation, could we build translated docs.nestjs.com website and host it anywhere? Would it be legal?

[rlaace423]

@ShGKme @Hwan-seok I think current master branch doesn't use content/ at all. Seems that It just renders html files inside each components.

So, it seems that more discussion required.
If direction is set, I'll start translation Korean. #890

[kamilmysliwiec]

Let's track this here #316