Summary for Docs Team Meeting on February 22, 2021

Attendance

@estelaris @atachibana @sasiddiqui @deadpool76 @bph @chaion07 @sukafia @tacitonic @justinahinon @aurooba

Housekeeping

Project Updates

End User 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. Editor team

Updates by @bph

  • Huge thanks for @geheren for working through the upcoming change with WordPress 5.7 and added it to the spreadsheet. Release is scheduled for March 9th, 2021.
  • Some line items are already claimed/assigned to contributors. Thank you @bizanimesh @collinsmbaka @cguntur @geheren to charge ahead!
  • If you’d like to work on some of it add yourself to the card on the TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board in the “need changes” column. (If you are not part of the Trello board yet, use this link)
  • Sprint is this week Thursday Feb. 25 – P2 post. If you want to learn more about the Full-site editing, also join this sprint.
  • The metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team is working on a scheduled update feature, so we can work on our pages on the site, without overwriting existing pages. It’s now in alpha-test and if you want to test it contact  @Corey McKrill to get you access. 

HelpHub Redesign

Updates by @estelaris

Changing the anchor # from documentation. As of now, if you are to read a title with a screen reader, for example “New to WordPress #” it will read “new to WordPress number” ,
The accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issue plus the visual noise caused by that # and the images are the reasons of changes. Will write up a post this week explaining this.

HelpHub issue

@deadpool76 found the wrong descriptions about PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. requirements. Though they were already fixed, multiple pages should not have the duplicate information. @atachibana will integrate duplicate requirement articles.

New Member Mentoring

🎉 Four new members joined the Docs channel in the past 7 days and were welcomed by @tacitonic.

Monthly Coffee Break

February’s Coffee break is scheduled for Thursday, February 25th, being planned by @sukafia and @chaion07; Find details here: https://make.wordpress.org/docs/?p=11101

Google Season of Docs

Updates from @tacitonic

  • Completed 12/28 articles in the Word list and usage dictionary.
  • Still waiting for the parser implementation – 1 week till I have to send a final project report to Google.

Open Floor

n/a

February 2021 Docs Team Coffee Break Announcement

The next Coffee Break for Docs Team is scheduled for Thursday, February 25, 2021, 11:00 UTC. The details for joining the Zoom call are as follows:

The details will also be posted in #docs channel on the day. If you wish to get a calendar invite then please 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.” @chaion07 or @sukafia. Take care and stay safe!

#coffee-break, #meetings

Agenda for Docs Team Meeting February 22, 2021

The next meeting is scheduled with the following details:

When: Monday, February 22, 2021, 03:00 PM GMT+1

Where: #docs channel on Slack.

Meeting Agenda

Project Updates
Full Site Editing Documentation
New Member Mentoring
Monthly Coffee Break
Google Season of Docs
Open Floor

Please feel free to suggest agenda items by commenting on this post or raise during the open floor.

Thank you!

Summary for Docs Team Meeting on February 15, 2021

Attendance

@collinsmbaka, @bph, @aurooba, @estelaris, @tacitonic, @atachibana, @chaion07, @crstauf, @sukafia, @poena, @themiked, @nahidsharifkomol

Housekeeping

Project Updates

End User 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. Editor team

Updates by @bph

Scheduled Sprint

February 25th, 2021 with two time slots, 14:00 – 16:00 UTC (9 to 11 EST) and 21:00 – 23:00 UTC (6 to 8pm EST)

  • To get the task list together, onboard new contributors, update TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. Cards, and progress follow up with experience contributors.. There will be a Zoom call with demos, screen sharing, and Q&A.

Updates for 5.7 release

  • @geheren and @bph have been working on identifying user facing changes and cluster them per section.
  • Updates are happening for existing pages with a link to the More Options page, and to reduce the duplicate content. When touching all pages, the feedback section is also opened up on all pages. @collinsmbaka and @bph will rally the troops on #meta-helphub
  • To Do: We need to come up with a process for the comments to tally them and see the nature of the problem and how to solve them.

Design

Updates by @estelaris

The comments for the requirements for a new design for user documentation were closed yesterday. There was a discussion with the design team about the anchor icon, in particular, and a decision was made to design a new icon to replace the current ‘#’ icon, further explanation can be found here.

@estelaris is working on the new navigation and post about that part, but needs help. There are many articles (at least 170) that need to be reviewed for old/broken links. To help review them:

  • View the list of articles in this Google doc, in the “List of Pages” tab. The results of the review should go into the “Link Review” tab.
  • Please do not fix any links, that is the job of @atachibana and his team, and any changes need to be approved by them
  • If you have any questions, 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.” @estelaris in Slack.

Full Site Editing Documentation

Transcript bookmark

Planning of Full-Site Editing (FSE) documentation is ongoing (for the 5.8 release). Contributors are needed who know FSE deeply and can teach the rest of the team how it’s supposed to work. Thanks to Tom Rankin for working on the outline. @bph will be publishing a blog post with a call for contributors.

Before the meeting, @milana_cap mentioned, “As a team, considering the way documentation is structured currently, we have to come up with our proposal where FSE (Full Site Editing) documentation should live.”

There was a healthy discussion around how the FSE documentation should be structured and how FSE should be defined. As @bph described, there are 3 parts to FSE documentation:

  1. Themes need to be built for it. A theme must support FSE for it to be available. This information needs to be available in the Developers Handbook.
  2. There is the user facing site for those who have access that should be in the User facing documentation on Help Hub.
  3. Documentation for site builders who build sites for others. There is no current space for this yet.

@poena pointed out there are a lot of overlaps between these 3 aspects, since users, site builders, theme developers, and theme designers all will use the editor to assemble blocks.

@themiked felt FSE should be a single page with links pointed towards discussions on how to use it within the desired context: theme handbook for themes, user handbook for users, etc. Ultimately, we can link to respective spaces when needed and create a bridge pages to interlink the different areas. The key issue here is to make the documentation easy to discover. @bph brought up the Fireside chat at WordCamp India, where @chanthaboune and @matt talk about FSE.

This is an undecided topic, which needs a dedicated post for feedback.

@bph will have a post out about user-facing documentation for FSE before February 25.

New Member Mentoring

🎉 Five new members joined the Docs channel this past week and were welcomed by @sukafia.

The mentorship team met last week Thursday on Zoom to plan and set goals for the year.
(If you’re not familiar with the team, you can read the initial proposal here to learn more.)

Monthly Coffee Break

February’s Coffee break is scheduled for Thursday, February 25th, being planned by @sukafia and @chaion07; a post with the zoom link and details will be published later this week.

Google Season of Docs

Updates from @tacitonic

Open Floor

Today is the last day to submit questions for the Full Site Editing call for questions.

Summary for Docs Mentorship Team Meeting on February 13th, 2021

The mentorship team is tasked with the responsibility of onboarding new members of the documentation team. You can learn more about the team’s responsibilities in the initial proposal.

On February 13th, 2021 the team met on Zoom to plan and set goals for the year.

Attendance

@sukafia, @chaion07 and @tacitonic

Team Goals for Q1 2021

  1. Automated 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/. bot to welcome new members with links to relevant resources.
  2. Add the mentorship team to the handbook
  3. Call word for mentorship (a word people can use in the slack channel that automatically pings members of the team)

Other plans/resolutions

  1. Welcoming new members during each docs team meeting 
  2. Monthly new contributors office hours (We hope to start this after the first quarter)

Your contributions/suggestions are welcome!

Agenda for Docs Team Meeting February 15, 2021

The next meeting is scheduled with the following details:

When: Monday, February 15, 2021, 02:00 PM GMT

Where: #docs channel on Slack.

Meeting Agenda

Project Updates
Full Site Editing Documentation
New Member Mentoring
Monthly Coffee Break
Google Season of Docs
Open Floor

Please feel free to suggest agenda items by commenting on this post or raise during the open floor.

Thank you!

Summary for Docs Team Meeting on February 8, 2021

Attendance

@austinsangs @sukafia @atachibana @justinahinon @kenshino @collinsmbaka @worldweb Francis Eichenlaub @tacitonic @bph @milana_cap @crstauf @chaion07 @estelaris

Housekeeping
Agenda: https://make.wordpress.org/docs/2021/02/08/agenda-for-docs-team-meeting-february-08-2021/
Notetaker: @milana_cap
Facilitator for the next meeting: @collinsmbaka
Next Meeting: Monday, February 15, 2021, 14:00 UTC
Find the complete Transcript of the meeting on 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/..

Team Goals for Q1 2021

We have team goals for first quarter of 2021 published. Everyone are welcome to leave comments if something should be updated or corrected.

Project updates

New Member Mentorship

The onboarding team will have a focused meeting on Thursday at 2PM UTC to plan and set goals for the year. We had 7 new members last week.

Monthly Coffee Break

@sukafia and @chaion07 will work on implementing these:

  • Write down what is expected from host and who to contact for possible questions (like we have for facilitating the meeting)
  • Try to get next host promised at the actual break

The time and date for the next Coffee Break will be announced on next meeting.

Google Season of Docs

@tacitonic reports that he has:

  • Completed all the main articles in the style guide.
  • Started with the word list and usage dictionary. As mentioned in the last meeting, this would most likely be a running article and words would be added as and when they are deemed to be important enough.

Everyone is welcome to review and leave feedback for the Style Guide here: https://github.com/WordPress/WordPress-Documentation-Style-Guide

Open floor

@tacitonic is asking if the team would prefer the full or shortened path for Style Guide. For example:

Leave your opinions in the comments below.

Agenda for Docs Team Meeting February 08, 2021

The next meeting is scheduled with the following details:

When: Monday, February 8, 2021, 04:00 PM GMT+2

Where: #docs channel on 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/..

Meeting Agenda

Team Goals for Q1 2021
Project Updates
New Member Mentoring
Monthly Coffee Break Summary (February 2021)
Google Season of Docs
Open Floor

Please feel free to suggest agenda items by commenting on this post or raise during open floor. Thank you!

#agenda

Summary of Docs Team Virtual Coffee Break: January 2021

The virtual coffee break for January happened on the 29th instant from 15:00 UTC to 15:30 UTC as per schedule. I facilitated the session with only Estela Rueda answering the call. We understand the fact that a lot of our regular contributors aren’t back from holidays yet and as the second wave of COVID is emerging in different parts of the world it is becoming a lot difficult that we can imagine for contributors to join in.

During the session we had a casual discussion about our lives and we tried to reflect on the collaborations that we contributed to during last year. We talked about family and friends including our journey for the documentation regarding the projects that we are working on. Personally it was great for me to receive first-hand advice from Estela about contributing to open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. and WordPress.

P.S. Even though Estela asked me not to write a p2 or post screenshots from our virtual coffee break, I thought it would be a good practice to continue with the tradition of having an update for the team. I hope she won’t mind. Thank you all and stay safe!

#coffee-break, #meetings

Agenda for Docs Team Meeting February 01, 2021

The next meeting is scheduled with the following details:

When: Monday, February 01, 2021, 14:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

  1. Team Goals for Q1 2021
  2. Project Updates
  3. New Member Mentoring
  4. Monthly Coffee Break Summary (January 2021)
  5. Google Season of Docs
  6. Open Floor

Please feel free to suggest agenda items by commenting on this post or raise during open floor. Thank you!

#agenda