Contributing guide as a page

[Chrissdroid]

Making the guide for contributing to docs available as a page (ex: /en/contributing or /en/guide/contributing), can address these issues:

• Allow translation into each language supported

• Allow translators to specify one or more detail about their opinion on the translation on this page (like a link to their glossary page, see Glossaries for translation ? #474)

• Allow direct link to this guide for easier sharing when someone want's to be part of the process

• I am willing to make a PR

Open to suggestions, as always !

[sarah11918]

I like this!

Would you suggest still having the i18n guide (Admittedly, I always have to hunt for this myself.) 😅 Would these pages be linked from there? Or do we consider making the main docs README bigger and include more?

There's still an advantage to having one central page, like the one we have now, so that we can have one place where we create it in English, and one place for us to maintain the "one true copy." Then, each language can have its own translated page, resources etc.

[Chrissdroid]

I was wandering this being both a guide for user willing to contribute to the translation as the "i18n guide" but translated to each language to break the language barrier (which can be a problem for some people ) and a guide for contributing to the docs itself

With every language choosing to add one or more section about their methods for translating

[sarah11918]

OK, so the suggestion is we make it as an English "page" (to replace the i18n .md README?) and then it fits into our existing workflow re: when the content needs updating in other languages?

How do we handle each language having some of their own, different content? Do we just use @hippotastic 's automation that when there has been an update to the English, each langugage will update their translation for that part. BUT, at the same time, each language page might have MORE, ADDITIONAL content (that does not match the English page)?

[Chrissdroid]

That's the idea, don't know exactly how hippo could make it work but i think it's more appealing for people via a dedicated page than a README on github (and more easy to share if needed to link it from a tweet or a message) and could let each language have their "unique" (at a certain degree) internal workflow enforcing certain writing style matching theirs method

[sarah11918]

+1 from me, I agree! No need to convince me. :)

I just want to make sure I understand what is being proposed, and how it will fit into what we have.

[hippotastic]

Hmm, I'm not sure if I'm happy with the idea of mixing public-facing and (primarily) internal content in one tool.

Just a quick alternative idea: What if we unlock GitHub's wiki feature for the docs repo? This would be a really simple way for translators to collaborate and it's fully searchable, linkable and right next to the translations on GitHub.

[sarah11918]

Great point, @hippotastic . I know that's where React's French glossary/resources are right now. And I also noticed that only /fr/ is using that there right now. @Chrissdroid - can you imagine something like this working?

[Chrissdroid]

Just a quick alternative idea: What if we unlock GitHub's wiki feature for the docs repo?

I actually thought of that with the i18n-fr team but it mean that we need each language to have their "ambassador maintainers" to have the right to edit theses and maintain them

( could be a pain for @sarah11918 or @delucis to edit everytime there's a change to be done, FOR EACH LANGUAGE 🤣 )

[sarah11918]

Hmm... can someone have Wiki editing permissions WITHOUT having merge permissions?

Note: Fred HAD mentioned designating one Language Lead person, so that idea is not that far off.

[hippotastic]

I volunteer as a tribute... for ambassador maintainer of the German translations at least. 😄

[sarah11918]

... and of course, giving one person per language merge permission is ALSO a possibility! (I think?) Didn't mean to say that it wasn't... just asking whether we can split it up that way.