Explore supporting different languages for our docs

[cindyorangis]

Docusaurus has a tutorial on the basics of the Docusaurus i18n system. I don't know any languages well enough to translate but if we had someone on the team willing to try this out, I help get this rolling. This would pave the way for Hacktoberfest contributors since it seems to be pretty popular to translate docs for that event. We can try a single doc first.

[humphd]

I wonder when the right time to do this is? I suspect that localizing fast-moving docs is going to be hard. Probably a goal of 3.0 should be to have the docs stay relatively stable for the 3.x lifecycle. In the 4.x lifecycle, we could revamp them.

That means, we should plan out what needs to get written between now and 3.0, and file those issues.

[cindyorangis]

I imagine this would be a post-3.0 thing since we're still waiting on a number of docs to be added:

• Document REST API #203
• Documentation for Supabase #2734
• Fixes Issue-2767: Windows installation steps to use expo-cli with android studios #2920
• We need to update the architecture.md  #2855 and Create Telescope Architecture Diagram #2880

and I'm sure there will be new docs that need to be written before 3.0

We also need to dogfood and audit the docs before they're ready to be translated

[sirinoks]

I'm down to translate to Russian

[humphd]

One thing I'm going to push people on re: translation, is that they have to build a team. Just like I wouldn't let a student drop a PR in some programming language none of us knows, there's no way I'm going to take a translation that I have to maintain without it also arriving as part of a team.

Years ago, a bunch of my Ukrainian students got together and translated the Rect docs as a team, see https://uk.reactjs.org/. It was inspiring to watch. We can do the same for Telescope, but we need to build some teams of people to do the work, and people to review, and ideally, people who want to help maintain it later.

[sirinoks]

There's a tool I saw used for Staxel translations, where it automatically makes tables with original and translation columns and it's really nice to use for non developers. I'm not sure what it was though..

[TueeNguyen]

Should this be closed? We haven't implemented the full feature

[aserputov]

@TueeNguyen I think this one closed automatically because I merged PR. Thanks.

[tpmai22]

We got this keeping track in #2962