Sagar Gurnani 6:56 pm on August 17, 2023
Tags: , ,   

Summary for Docs Team Meeting (15-Aug-2023)

Attendance

@milana_cap @leonnugraha @sagargurnani @ninianepress @marcio-zebedeu @kartiks16 @611shabnam @estelaris @cold-iron-chef @huzaifaalmesbah @shuvo586 @pratikshrestha @noumantech @femkreations (async)

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming Meeting

The next team meeting will be the “Docs Online Contributors Day” as a WCUS followup and would be held on Aug 29, 2023 at 14:00 UTC.

Next week (22-Aug-2023) is supposed to be the Docs Online Contributors Day but is cancelled as it’d the same week as WCUS and Community Summit.

Project Checks

@milana_cap created a new workflow for this GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repo.

@sagargurnani completed #935 which was reviewed by @atachibana.

@atachibana reviewed #811, #934, #935. Closed #753, #754, #759,  and is now working on #760.

@611shabnam is working on #678.

@cold-iron-chef is working on #278.

@estelaris mentioned that there would be a x-post regarding the translation of content in the .org. It will be on the polyglots make blog and if anyone contributes to his local translation teams then he should check that post. There are several issues which are needed to be resolved translation is started.

Open Floor

@cold-iron-chef asked about getting the “Documentation Contributor” badge on her profile and @milana_cap helped her out with that.

@estelaris asked the contributors their point of view on topics for the summit and said that the team would do its best to take that point of view to the summit. Discussion topics can be found here.

#docs, #meetings, #summary

Estela Rueda 4:34 pm on August 15, 2023
Tags: ,   

X-post: Discussion for a proposal for WP.org content translation and localization

X-comment from +make.wordpress.org/polyglots: Comment on Discussion for a proposal for WP.org content translation and localization

Leonardus Nugraha 6:11 am on August 15, 2023
Tags: ,   

Agenda for Docs Team bi-weekly meeting August 15, 2023

The next meeting is scheduled with the following details:

When: Tuesday, 15 August 2023, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Upcoming meeting and Docs Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. schedule
  3. Note-taker and facilitator selection for the next meeting
  4. Facilitator selection for the next triage meeting
  5. Project check
  6. Open floor

If there’s anything you’d like to discuss on the open floor, please leave a comment below.

#agenda, #meetings

Hari Shanker R 2:32 pm on August 11, 2023
Tags: ,   

X-post: The Inaugural Cohort of the WordPress Contributor Mentorship Program has Concluded

X-comment from +make.wordpress.org/project: Comment on The Inaugural Cohort of the WordPress Contributor Mentorship Program has Concluded

Mushrit Shabnam 9:31 am on August 4, 2023
Tags: , ,   

Summary for Docs Team meeting, August 1, 2023

Attendance

@leonnugraha @milana_cap @femkreations @sagargurnani @anandau14
@bph @themiked @estelaris @atachibana @611shabnam @rashiguptaa
@cold-iron-chef @JoMinney (async)

Housekeeping

Project Checks

@atachibana and @Alvaro Gómez /mrfoxtalbot  fixed this issue.

@leonnugraha tagged all 6.3 user docs issues with tracking issue and new document labels accordingly.

@611shabnam completed #687 and #282 and @femkreations closed those tickets.

@anandau14 prepared the draft of Page List BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., received the access of docs site, will publish the prepared docs soon.

@milana_cap created few new issues from HelpHub feedback, added another workflow for GH (applying developer label one other devhub labels are applied), finished and published post for core dev blog, did onboarding session with @ninianepress

@femkreations 1st and 2nd reviewed #687 and #282 and scheduled the articles for publishing, 1st reviewed #676, reviewed all the pages under #899 for replacing the Reusable blocks to Patterns and closed. Did a 2nd review of #949 and closed it. Onboarded a new contributor for #986 and created tracker for consolidating More rich text editing options #986. Moved few more tasks to the 6.3 from 6.2 board

@cold-iron-chef is working on #161

@femkreations mentioned we still have work to be done before August 8th. The tasks have been sorted into medium priority tasks and high priority tasks on the 6.3 project board. If you are new to the Docs team, you can select from the list of good first issues.

Question: How to open an issue

@cold-iron-chef noticed there’s no Vimeo Block documentation at all and asked how she can open issues. @estelaris informed she should go to this link and confirmed no permission is required. Later @cold-iron-chef confirmed she will be adding that link to the list of embeds.

Question: Move closed tasks automatically to the Done column in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/

@milana_cap mentioned it should work automatically but @femkreations mentioned it is not possible to do so in 6.3 board. So cold-iron-chef mentioned that if we tag the pull request with closes #
 it will close the issue when that’s merged.

@milana_cap mentioned @stevenlinx created the board, so may be he can take a look. Also she mentioned closing the tickets from repository should move the tickets automatically.

@femkreations confirmed that the problem exists even when the tickets are closed from repository and it only exists for 6.3

@estelaris jumped in and asked if we shall create a page in the handbook with instructions on how to create boards with all the bells and whistles you like, for release leads? @milana_cap and @femkreations agreed on this. So, @estelaris asked if @femkreations can open the issue and add the bells and whistles. @femkreations confirmed she will do that.

@femkreations created this issue in response and @stevenlinx chimed in after the meeting and mentioned he added the features as needed. It’s in Workflows of the Project: when an item is closed or a PR is merged, set Status to Done. He asked @femkreations to check. @femkreations confirmed the issue is fixed and the issue moves automatically to the Done column.

@femkreations made some updates to the 6.3 Project board columns. We now have a new Edit after 1st Review  which means waiting for the content edits after the 1st Review. Makes it easy to see the progress at a glance.

Open Floor

It was birthday of @estelaris and she was in Venice! Happy Birthday @estelaris!

@femkreations said: “Big thanks to @atachibana @Alvaro Gómez /mrfoxtalbot @Leonardus Nugraha @611shabnam @Anand @poena for working on the 6.3 tasks for the upcoming release. We still have work to be done before August 8th. Please check out the 6.3 project board. The tasks have been sorted into medium priority tasks and high priority tasks. If you are new to the Docs team, you can select from the list of good first issues.

#docs #meetings #summary

Jenni McKinnon 10:19 pm on August 1, 2023
Tags: , ,   

Summary for Docs Team meeting, Jul 18, 2023

Attendance

@ninianepress @milana_cap @leonnugraha @jominney @611shabnam @jyolsna @atachibana @femkreations @sumitsingh

Housekeeping

Find the complete Transcript of the meeting on Slack.

Upcoming meetings

The next team meeting will be the monthly online Contributor Day which will be held on Jul 25, 2023 at 13:00 UTC.

Project checks

@milana_cap:

  • helped a bit with WordPress 6.3 docs
  • working on nonces coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev blog post

@femkreations:

@leonnugraha:

  • Has been wrangling, reviewing, and publishing WordPress 6.3 dev notes, mainly for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ with @milana_cap and @bph‘s help

@611shabnam:

  • Completed #282

@jyolsna:

  • Reviewed a 6.3 doc

Open floor

There were a few mentions and discussions on important issues:

Meeting adjustments for August

As WCUS is coming up in August, the team decided to adjust some meeting dates to accommodate team contributors who will be in attendance.

As such, the meeting on Tuesday, 22 August, 2023 will be an asynchronous meeting in the #docs channel on Slack for WCUS Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..

The monthly online Docs Team Contributor Day that was previously scheduled for August 22 has now been moved to Tuesday, 29 August, 2023 from 13:00-16:00 UTC.

Call for volunteers announcement and amplification

@femkreations almost has the announcement post calling for volunteers to work on the 6.3 Documentation Project Board.

She requests that once the post has been published, that the team shares it to help spread the word to get more contributors.

Headings and bold text in articles

@611shabnam noticed that some articles have headings that are bold instead of actually being formatted as headings and asked for the protocol.

@femkreations and @leonnugraha answered:

  • Generally, we use headings H1 through H3
  • Bold is used for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. names or to describe screen names and such

#docs, #meetings, #summary

Pooja Derashri 5:12 am on August 1, 2023
Tags: ,   

X-post: What’s new on Learn WordPress in July 2023

X-comment from +make.wordpress.org/updates: Comment on What’s new on Learn WordPress in July 2023

Leonardus Nugraha 2:33 am on August 1, 2023
Tags: ,   

Agenda for Docs Team bi-weekly meeting August 1, 2023

The next meeting is scheduled with the following details:

When: Tuesday, 1 August 2023, 02:00 PM UTC

Where: #docs channel on Slack

Agenda:

  1. Attendance
  2. Note-taker and facilitator selection for the next meeting
  3. Facilitator selection for the next triage meeting
  4. Project check
  5. Open floor

If there’s anything you’d like to discuss on the open floor, please leave a comment below.

#agenda, #meetings

Jenni McKinnon 1:30 am on July 24, 2023
Tags: ,   

Online monthly Docs Team Contributor Day July 25, 2023

The Documentation Team holds an online, monthly Contributor Day on the fourth Tuesday of every month. Any one may join who wishes to contribute to the team and who follows the Code of Conduct.

The next Docs Team Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

The next monthly online Docs Team Contributor Day will be:

When: Tuesday, 25 July 2023, 1:00-4:00 PM UTC

Where: #docs channel on Slack, and on Zoom.

Please also see Contributor Day — 25 July, 2023 on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ for onboarding and other important details.

Onboarding on Zoom

In addition to the details in the GitHub issue for this Contributor Day, folks who are in need of onboarding can ask in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. or on the Zoom call. In Zoom, a breakout room will be started where contributors can be onboarded.

If at any time you have any questions, please feel free to ask in the #docs channel on Slack or in Zoom throughout the day.

After Contributor Day

Other than celebrating with some 🍪🍪🍪 after Contributor Day is over, please also comment on the corresponding GitHub issue with:

  1. 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/ profile username
  2. What you worked on and include links when possible.

Or, just comment anything (such as your WordPress.org username) to let the team know you attended.

#contributor-day, #docs

Femy Praseeth 2:48 pm on July 18, 2023
Tags: 6.3, ,   

Call for volunteers to help with 6.3 end-user documentation

The Docs team needs your help to update and revise the End User Documentation (HelpHub) for the upcoming WordPress 6.3 release, expected on August 8th, 2023.

You can find a list of all the tasks in the 6.3 project board in the Documentation’s repo on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

The tasks have been sorted into medium priority tasks and high priority tasks. The team plans to complete the high priority tasks by the 6.3 scheduled release date.

How you can help

If you are new to the Docs team, you can select from the list of good first issues.

If you are new to contributing to WordPress, you can review this onboarding post with training videos and links to help you get started.

Once a task is assigned to you, the following two videos show how to help with updating the existing articles in End User Documentation (HelpHub).

Video onboarding to End User documentation

Video showing how to help with updating the existing articles on GitHub (referencing 6.2 in this video)

Once you complete the updates for the task, add a comment to the issue you worked on, noting that you have made the changes, and tag the Docs team (@femkreations, @Leonardus-Nugraha or @jennimckinnon). Someone from the Docs team will review the updates and add the content to the article. 

If you have questions or need help, ask in the docs channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. or directly in the GitHub issue itself.

If your meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. or company can give a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. of time to help, do include the Release co-leads for 6.3 documentation in your message: (Slack IDs) @Femy, @Leonardus Nugraha, @611shabnam.

Resources

If you need a test site with WordPress 6.3 pre-installed, you can use this app provided by InstaWP to spin up a new temporary website set. It is preloaded with Theme Test data and other pre-configuration, ready to go. This new site will be available to use for four hours. After that, if you need another test site to contribute to docs, you can visit the link again and create a new temporary site.


Props to @leonnugraha for reviewing this article.

#6-3, #docs, #helphub