Opened 23 months ago
Last modified 12 months ago
#6714 new enhancement
es_ES (es.wordpress.org) Handbook sync
Reported by: | JavierCasares | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | International Sites (Rosetta) | Keywords: | |
Cc: |
Description
Some time ago, the Spanish Team asked having the possibility be part of this early stage of HelpHub & Handbooks Localization https://meta.trac.wordpress.org/ticket/4572
There is this Handbook https://github.com/WPES/spain-handbook prepared to be moved to the WordPress organization at GitHub, and to be synced with "the tool" to the Spanish Handbook at https://es.wordpress.org/team/handbook/
There is a manifest to start the syncronization at https://github.com/WPES/spain-handbook/tree/master/assets/bin/handbook-manifest.json
To-Do:
- Migrate https://github.com/WPES/spain-handbook to https://github.com/WordPress/spain-handbook
- Allow @javiercasares access to the repo
- Allow @javiercasares to https://es.wordpress.org/team/handbook/
- Sync the new repo with the site
After that the Spanish Team will so a first review, check that everything works fine, and start adding more content (now there will be only one manual about how to use GitHub to publish).
cc/ @estelaris @glycymeris @anagavilan @bertaminguela @davidperez @nao
Change History (12)
This ticket was mentioned in Slack in #docs by javier. View the logs.
22 months ago
This ticket was mentioned in Slack in #docs by javier. View the logs.
21 months ago
This ticket was mentioned in Slack in #meta by javier. View the logs.
21 months ago
This ticket was mentioned in Slack in #meta by javier. View the logs.
18 months ago
#7
@
17 months ago
Hi! We are trying to translate the Handbook into Japanese as well. I would like to share how we are doing.
- Use wp-handbook-converter
https://github.com/mirucon/wp-handbook-converter
This is a library to get WordPress Handbook via REST API and convert it to markdown.
Very useful! Thank you @mirucon
- Make a GitHub repository of markdown files obtained in 1.
- Manage the progress of each page by Issue
- Translate, and PR
Little Tips: By enclosing the original text you want to translate with comment-out tags with line breaks, you can easily see the differences on GitHub.
- merge after review. Repeat 4 to 5
If there are any updates to the original, use the wp-handbook-converter again to get the differences and update them.
So, Thanks to great help we manage to try, but it is far from ideal.
For example, it is more complicated than translating WordPress itself, and it limits the number of people who can be involved. If there is a better way, we would like to improve it.
Thank you!
cc. @nao @atachibana @wildworks
#9
@
13 months ago
As the project has started (and we are moving, temporary, manually the content from GitHub to WordPress), at least, is possible to do the 1 and 2?
- Migrate https://github.com/WPES/spain-handbook to https://github.com/WordPress/spain-handbook
- Allow @javiercasares access to the repo
I have access to the Handbook / Team Site, so that's not a problem now, and we may need to wait until #7347 to have the synchronization.
#10
@
13 months ago
It's been a long road but, we just moved all our "old content" to the Handbook!
https://es.wordpress.org/team/handbook/
I know we cannot sync yet (because #7347) but, people are going to work in the repo, and should be great to have the GitHub-Profile in use for the contributions.
Can we move https://github.com/WPES/spain-handbook to https://github.com/WordPress/spain-handbook and leave everything there until the sync can be made?
After this weekend meetings with @estelaris and @anagavilan, we approved a PR to reorganize and prepare everything to be published in the Handbook Plugin at es.wp.org/team/handbook.
Before doing that, the first step should be to transfer WPES/spain-handbook to WordPress/spain-handbook.
I have permission to transfer the repo, so we can send it to @dd32 and the be transfer to the WordPress organization.
After that, currently the only “full” access we will need is for javiercasares, anagavilan, and jesusyesares (GitHub usernames).
There is one possible manual to be published now, but we will stop that part until WordCamp Europe 2023 to do a full review between the Spanish Team, the Docs Team, and the Meta Team.
cc: @estelaris @glycymeris @anagavilan @milana_cap