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

Sign-off english content to be translated #267

Closed
IstoraMandiri opened this issue Dec 7, 2019 · 5 comments
Closed

Sign-off english content to be translated #267

IstoraMandiri opened this issue Dec 7, 2019 · 5 comments
Labels
content adding or changing current info i18n Internationalisation Release

Comments

@IstoraMandiri
Copy link
Collaborator

IstoraMandiri commented Dec 7, 2019

Before we accept translations contributions, we should whitelist sections of the English version that are deemed "final" and good enough to be translated into the many other languages. So far the content has not been verified in its entirety by more than one person. Much of the content that was copied over may be out of date, and some content is still pending updates (#261 #235 #260 #244 #241 #186).

In light of this, we can focus on the content that is ready. Please use this thread to confirm which pieces of content on the current staging site content are good enough to be translated.

https://staging--ethereumclassic.netlify.com/

I will use this thread to reference when implementing #246 and #245.

Only "signed off" content will be shown to translators, and will otherwise not be shown to translators (as it's liable to change and would be a waste of time to translate).

Again, until content has been signed off in this thread we should not have it translated.

I await your suggestions on how many people should be required before the content is considered signed off.

@IstoraMandiri IstoraMandiri added i18n Internationalisation Release content adding or changing current info labels Dec 7, 2019
@IstoraMandiri IstoraMandiri added this to To do in Web Development via automation Dec 7, 2019
@IstoraMandiri IstoraMandiri moved this from To do to In progress in Web Development Dec 7, 2019
@bobsummerwill
Copy link
Member

Thanks, Chris.
I will try to find time on Sunday to give a final opinion from me on "must do" content fixes. Perhaps best as a PR actually making changes I think we need.

@TheEnthusiasticAs
Copy link
Member

The infrastructure and content parts are ok for me. Nothing found since the last time I mentioned points on the etc discord :)

@IstoraMandiri IstoraMandiri moved this from In progress to To do in Web Development Jan 14, 2020
@IstoraMandiri
Copy link
Collaborator Author

IstoraMandiri commented Jan 21, 2020

Presently, this is being managed in the wiki

https://github.com/ethereumclassic/ethereumclassic.github.io/wiki

I also created a project just for content management https://github.com/ethereumclassic/ethereumclassic.github.io/projects/2

Contributors, please contribute!

@IstoraMandiri IstoraMandiri removed this from To do in Web Development Jan 21, 2020
@IstoraMandiri IstoraMandiri pinned this issue Jan 21, 2020
@IstoraMandiri IstoraMandiri moved this from Doing to English Content (via Wiki) in Content Management Jan 21, 2020
@gitr0n1n
Copy link
Contributor

i'm updating the wiki with information gathered on my ecosystem deep dive.

@IstoraMandiri
Copy link
Collaborator Author

I'm closing this issue now as we're pretty much wrapped up on english other than news updates.

@IstoraMandiri IstoraMandiri moved this from English Content (via Wiki) to Added to site in Content Management May 26, 2020
@IstoraMandiri IstoraMandiri unpinned this issue May 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content adding or changing current info i18n Internationalisation Release
Projects
No open projects
Content Management
  
Added to site
Development

No branches or pull requests

4 participants