Kicking off the Community Documentation/Translation Sprint from September 20 to 24

As announced previously, the Community Team is launching a week-long documentation sprint (focussed on translations), as part of the International WordPress Translation Day celebrations! From today (September 20) through September 24, community contributors and deputiesDeputy Community Deputies are a team of people all over the world who review WordCamp and Meetup applications, interview lead organizers, and generally keep things moving at WordCamp Central. Find more about deputies in our Community Deputy Handbook. will work together to update Community team handbooks, with a focus on translating them (and related Community Team documentation pages) to local languages! The sprint is open to all, and we warmly welcome everyone to participate!

Of the highest and most immediate impact, the 2021: Return to In-person meetups handbook section and the recent announcement on the return of in-person WordCamps and updated guidelines need attention. If you are looking for a document to start translating, we recommend that you prioritize these pages, due to the importance of these updates.

Want to find out more about the event and learn how to participate? Check out the announcement post for more context and details:

We also have an excellent Tuesday Training which will guide you on how to translate community team documents:

How do I participate in the translation sprint?

Anyone can participate in this initiative! The team will keep track of edits in a Google Sheet. Please log all the changes you make in that sheet. The team will also coordinate together in the #community-team channel. You can also share your updates in the #polyglots-events channel to connect with fellow Polyglots.

If you are new to translating handbooks, check out this Tuesday Training that will answer all your questions. Anyhow, here is a suggested workflow for contributors:

  1. Find a documentation page from the Community Team handbook that you wish to translate.
  2. Check the tracking sheet if anyone else is working on it for your locale. If your locale has already translated handbook pages, check your locale’s Rosetta site to see if anyone has already translated the page – you might also want to check with other community members to see if anyone is working on the docs. If no one is working on the doc and it has not been translated, log it in the sheet. Don’t forget to add the handbook and page names, and your WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ username!
  3. Copy the contents of the page over to a new Google doc. Ensure that its sharing permissions are set to: “Anyone with the link can comment”. If you already have access to your Rosetta site, you can copy the contents over to your locale’s handbook and make changes over there. Feel free to ask in #community-team if you have any questions about any contents in the documentation.
  4. Once you have finished translating the document, you can optionally pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” one or more of your team members to ask for review. Once the document is finalized, you can go ahead and publish the same in the handbook. If you prepared the translations in a Google Doc, don’t forget to share the same with your Locale Manager(s) or GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor.(s) so that they can update the same on your behalf.
  5. Fill up the spreadsheet to record the changes that you have made and update the field if the translated page was merged.
  6. That’s it, you have successfully made your first contribution to the Docs translation sprint! You can now proceed to work on the next document!

Remember: Every contribution, however small, is valuable!

But… I’m not a Polyglot and I would like to participate! What do I do?

We are glad you asked! While the focus of this sprint is translation, we need your help in reviewing our existing documentation, suggesting changes, and even creating new documentation pages. Even though the tracking Google sheet is aimed at translations, you can use the same to track your documentation updates too.

Of the highest and most immediate impact, the recent announcement on the return of in-person WordCamps and updated guidelines needs attention. You can help us out by creating a handbook page out of the announcement and making the guidelines more visible.

Check out the announcement post of the original docs sprint to learn more about how to update Community Team documentation:


I warmly welcome you all once again to join us in this initiative and to help us update our documentation and translate it into as many languages as possible. It will go a long way in supporting the WordPress community!

#documentation-sprint #translation-sprint #sprint #wptranslationday

+make.wordpress.org/polyglots

Announcing a WordPress Community Translation Sprint on September 20 – 24!

One of our Community Team goals for 2021 was to translate our Community handbook into different languages. We officially started work on translating our handbooks to different languages as part of past documentation sprints. I would like to extend our efforts by using the Translation Day Celebrations as an opportunity to translate our handbooks to as many languages as possible. 

Towards this, let’s plan another Documentation sprint (focusing on translating Community team content) from September 20 – 24, 2021, in conjunction with the WordPress Translation Day celebrations organized by the Polyglots team! (Thanks for the idea, @evarlese!)

What is the Community Translation sprint?

From September 20 through 24, community contributors and deputiesDeputy Community Deputies are a team of people all over the world who review WordCamp and Meetup applications, interview lead organizers, and generally keep things moving at WordCamp Central. Find more about deputies in our Community Deputy Handbook. work together to translate Community team handbooks and any related documentation for the Community Team to their local language. This differs slightly from the traditional docs sprints we have organized before in that our focus will be on translation. If you are proficient in a non-English language, feel free to join us and help translate the Make/WordPress Community handbook to your local language!

Please note: This translation sprint is restricted to the community team handbook pages – we will not be working on the official wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ documentation as part of this sprint. However, if you wish to translate wordpress.org documentation and need help, please reach out to your local translation team, or simply pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in #polyglots

Read on to find out more!

Continue reading

#documentation-sprint, #sprint, #translation-sprint, #wptranslationday

Join the Community Team for a Documentation Editing Sprint on May 25!

This contribution sprint has concluded! Together contributors made 35 major edits to the docs, including making changes to existing docs, and creating new docs pages. Most changes were made to the Online Event documentation and the Community Deputy Handbook. Thank you all for your contributions. We will be organizing more such docs sprints in the future. Stay tuned!

In light of the positive feedback on the documentation sprint proposal, I’m happy to announce that the Community team is going ahead with our first Documentation Editing sprint, all-day on Tuesday, May 25th! 🎉 All are welcome to contribute to this initiative. This post contains everything you should know about the documentation sprint, along with details on how you can contribute!

What is a documentation editing sprint?

All-day on May 25th, Community contributors and deputiesDeputy Community Deputies are a team of people all over the world who review WordCamp and Meetup applications, interview lead organizers, and generally keep things moving at WordCamp Central. Find more about deputies in our Community Deputy Handbook. work together to audit and edit outdated pages in the Community team handbooks and any related documentation so that they provide accurate and up-to-date information for community members. Check out the original proposal for more details and context.

What documents need editing?

All Community team handbook contents need auditing, reviewing, and updating. This includes (but is not limited to): 

Of the highest and most immediate impact, the Online Events Handbook needs attention since there have been significant changes to the online WordCamps program of late!

Additionally, one of our goals is to translate our handbooks to different languages. @mpcdigital and @nao will start working on this as part of this sprint (others are more than welcome to join if interested!) If anyone is interested, it would also be great to add some Tuesday Trainings to our handbooks!

How do I participate in the documentation sprint?

Anyone can participate in this initiative! The team will keep track of edits in a Google Sheet. Please log all the changes you make in that sheet. The team will also coordinate together in the #community-team channel.

There are a few ways to contribute to the sprint:

  • Triage: Go through the list of documents, make a note of the pages that need updating (as well as the changes that need to be made), and add them to the tracking sheet.
  • Editing: Editing the documentation pages to keep them clear and up-to-date.
  • Adding new content: This could include adding Tuesday Trainings to handbooks or translating existing content to new languages. If you feel that a new page on a specific topic needs to be added to the handbook, now would be an excellent time to contribute!

To track changes, copy the handbook contents over to a shared Google document, propose the changes over there (make sure the changes are highlighted), and link the document to the shared Google tracking Sheet.  Deputies will review and merge those changes later. More details in this page!

Try your best to follow the docs style guide while creating content, as it helps maintain consistency. This is an all-day event, and there is also no time commitment – try to spend as much time as possible on May 25th towards editing documents – even if you only have a few minutes.

Every contribution, however small, is valuable!

What’s next, once the event is over? 

Community deputiesDeputy Community Deputies are a team of people all over the world who review WordCamp and Meetup applications, interview lead organizers, and generally keep things moving at WordCamp Central. Find more about deputies in our Community Deputy Handbook. will review the contributions and merge all the changes that were proposed. The Community team will publish a recap of this initiative requesting feedback from contributors. If the event turns out to be a success, more of these sprints can be organized in the future!

I warmly welcome you all once again to join us in this initiative and to help us improve our documentation. It will go a long way in supporting the WordPress community!

#sprint

#documentation-sprint

#translation-sprint