Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translate docs #12396

Open
calpa opened this issue Mar 8, 2019 · 13 comments

Comments

@calpa
Copy link
Contributor

commented Mar 8, 2019

Summary

GatsbyJS has brings me a lot of awesome function to build modern website, and I initiated the idea of translating the docs into Chinese version in order to promote it.

Should I copy the docs and start a doc project, or other?

@lannonbr

This comment has been minimized.

Copy link
Member

commented Mar 8, 2019

This sounds like a great idea. So @jlengstorf actually had a livestream about building sites that had internationalization support with GraphCMS (Livestream VOD for reference). That said, the website doesn't part

The docs has a huge amount of content, and I think it would be a good step to start building it out in other languages such as Chinese.

@gatsbyjs/docs @gatsbyjs/website, Is there anything on the roadmap yet for i18n support? It would be a large undertaking but could greatly bring a large amount of developers to the community who may not be native english speakers or extremely fluent with the language.

@calpa

This comment has been minimized.

Copy link
Contributor Author

commented Mar 8, 2019

reactjs.org has build different repo for different language, maybe we can consider this approach

For simplified Chinese, they build this one:
https://github.com/reactjs/zh-hans.reactjs.org/
https://zh-hans.reactjs.org/

My team and I can contribute to this

@LekoArts

This comment has been minimized.

Copy link
Contributor

commented Mar 8, 2019

We closed such issues in the past as our stance on that topic was that we don’t want to have translated docs (yet). @marcysutton can make a call on this as I'm not sure if that situation has changed.

@m-allanson

This comment has been minimized.

Copy link
Member

commented Mar 8, 2019

I think having translated docs is a great idea!

In the past we've not had a good way to publicise translations or keep them up to date. This resulted in occasional docs getting translated but the translated files were tucked away in a folder in the repo, there was no way for people to find them from gatsbyjs.org. This resulted in very few people knowing they existed, which led us to the decision that no translations are probably better than outdated/incomplete and hard-to-find translations.

The React team's approach seems pretty sensible and scalable: https://reactjs.org/blog/2019/02/23/is-react-translated-yet.html

This will need some set up from the Gatsby team, so it'd be a case of working out if and when we can make the time for that initial setup work.

@laozhu

This comment has been minimized.

Copy link

commented Mar 8, 2019

Great idea, let's make gatsby docs easier for lots of Chinese developers.

@gatsbot gatsbot bot added the stale? label Mar 29, 2019

@gatsbot

This comment has been minimized.

Copy link

commented Mar 29, 2019

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

Thanks for being a part of the Gatsby community! 💪💜

@calpa

This comment has been minimized.

Copy link
Contributor Author

commented Mar 30, 2019

@m-allanson @lannonbr Any update?

@KyleAMathews

This comment has been minimized.

Copy link
Contributor

commented Mar 30, 2019

We definitely want to do this but no updates yet.

@KyleAMathews KyleAMathews added not stale and removed stale? labels Mar 30, 2019

@KyleAMathews KyleAMathews changed the title Translate Docs into Chinese Translate docs Mar 30, 2019

@KyleAMathews KyleAMathews added this to To prioritize in Learning Roadmap Mar 30, 2019

@prestonso prestonso self-assigned this Apr 15, 2019

@prestonso

This comment has been minimized.

Copy link
Contributor

commented Apr 16, 2019

Happy to say that we're beginning work on an official docs i18n process now!

Right now we're deciding whether it will need to be scoped to the full site or just the docs, but any suggestions about recommended approaches and whether folks find the routes taken by e.g. React and Vue would also be very welcome!

@jlengstorf

This comment has been minimized.

Copy link
Member

commented Apr 19, 2019

@prestonso this seems like it's probably a good candidate for an RFC — we'll have a lot of different things to iron out and get feedback on before we can start work. Maybe you and I can set some time aside to run through ideas and get the initial RFC written up?

@marcysutton marcysutton moved this from To prioritize to Backlog in Learning Roadmap Apr 24, 2019

@jlengstorf jlengstorf moved this from Backlog to To prioritize in Learning Roadmap May 13, 2019

@marcysutton marcysutton moved this from To prioritize to Parking lot in Learning Roadmap Jun 20, 2019

@alexandrtovmach

This comment has been minimized.

Copy link
Contributor

commented Jul 17, 2019

Is any progress with that? What about CrowdIn?

@alexandrtovmach

This comment has been minimized.

Copy link
Contributor

commented Jul 17, 2019

I started working on Russian and Ukrainian translations of Tutorials. If we going to have a plan to make global process I'd be in! Let me know how can I help.

@alexandrtovmach

This comment has been minimized.

Copy link
Contributor

commented Aug 6, 2019

@prestonso Hey! Any progress with that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.