Summary for Docs Team Meeting on 16 November 2020

Attendance

@chaion07 @kenshino @tomford @collinsmbaka @leogermani @obt28 @tacitonic @mkaz @atachibana @FahimMurshed @Veralee @hellofromtonya @justinahinon @estelaris @themiked @paaljoachim

Housekeeping

Agenda: https://make.wordpress.org/docs/2020/11/16/agenda-for-docs-team-meeting-november-16-2020
Notetaker: @justinahinon
Next Meeting: 23 November 2020
Find the meeting transcript here

Project updates

@atachibana gave an update of the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. and re-routing of Codex to Code Reference:

HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.: 153 of 355 (43.1% < – 33.8%). They’re also editing each method information of class references.

@bph mentionned prior to the meeting they’ll post asynchronously a digital check-in for the documentation team.

@justinahinon posted a follow up of 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/ developer documentation restructuring proposal.

Meeting times

@kenshino mentionned the Doodle for the documentation team meeting time. Please fill it if you haven’t yet.

New Member Mentoring

There were no update for this item.

Coffee Break November

The next coffee break will take place on the 19th of this month at 10am UTC. Here is the link if you want to add it to your calendar: https://us02web.zoom.us/j/83074914582?pwd=RlJkMkdnbzdKODZYbENzeUpXWGF2QT09.

If you want a Google Invite for the coffee break, you can also send a private message to @estelaris 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/..

You can also find all the details in this P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post: https://make.wordpress.org/docs/2020/11/16/docs-team-coffee-break-november-update.

Google Season of Docs 2020

@tacitonic made some updates about the progress on this project:

On the reclassification front, the team is still reviewing articles for content errors but have already finalized the title change. More details are in this spreadsheet: https://docs.google.com/spreadsheets/d/1_Ea2yeF5Rfy_YDk7pBRJ4rdljhMjygXFqBq8gWwhbaE/edit?usp=sharing.

The team also discussed the big problems with titles which is the use of gerunds (words ending in ‘ing, as in working, reading, etc). This discussion can be found here.

Docs Handbook and facilitating collaboration

@themiked shared last week some updates on legacy docs which @kenshino is reviewing.

@paaljoachim asked if there have been any talks about refreshing the design. As using bigger fonts gives more space and better readability.

#meeting-notes, #meetings, #summary

Digital Check-in for 🐝-docs team week November 2, 2020

Our Digital Check-in for this week:
Please share the following in the comments:

  • What did you work on last week?
  • What would you like to work on this week?
  • What are your blockers (things that stand in your way of your work) ?

Documentation Update Sprint to bring pages to 5.5 /5.6 version

We still have quite a few pagess on the 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 documentation that are still on 5.0 – 5.4 version. Let’s do an update spring on November 25, 26 and 27, 2020. Please let me know in the comments if you’d like to participate.

This week is release week:

  • WordPress 5.6 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3 is scheduled for November 2. You can get a preview of the upcoming version via the WordPress Beta Tester plugin
  • 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/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 9.3 will also be published later today (Nov 2). Some commits will be backported to WordPresss 5.6
  • Gutenberg plugin 9.3 release is scheduled for November 4th.

Our reading list for this week:

Contributor Links

Looking forward to ‘seeing’ many of you at the next 🐝 docs Slack meeting on November 9, 2020 at 13:00 UTC <- changed the meeting time an hour earlier on Monday. Where we will discuss among other things, above mentioned “Update Sprint”

HelpHub Feedback Section – new feature for contributors

At Docs team, we are putting a lot of effort into onboarding process and helping contributors to get started. One of those efforts is a “Feedback Section” for HelpHub (end user documentation).

Feedback section is resembling the User Contributed Notes section at DevHubCode Reference, so this is a comment section but with a difference of HelpHub’ Feedback Section not being publicly visible.

What is it for?

Feedback section is meant to help contributors report issues such as typos, out of date info, missing facts etc. Even though this feedback is not publicly visible, it is not anonymous. The contributor has to be logged in to send feedback. If logged out, visitor will see the message “Please log in to leave the feedback”.

Where is this feedback visible then?

This feature is enabled on HelpHub and all Rosetta sites with HelpHub enabled.

All the feedback can be found in dashboard’ comments section. It doesn’t really matter if you approve them or not so you can use this status system as a sort of tracking issues system.

We hope this will reduce the gap between new or passing by contributors and the team; and mimic the ease of contributing at Codex.

Complete discussion and the code can be found here: https://meta.trac.wordpress.org/ticket/4915

Digital Check-in for 🐝-docs team week October 19

Our Digital Check-in for this week:
Please share the following in the comments:

  • What did you work on last week?
  • What would you like to work on this week?
  • What are your blockers (things that stand in your way of your work) ?

This week is release week:

  • WordPress 5.6 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is schedule for October 20, which starts the beta/rc release testing phase. You can get a preview of the upcoming version via the WordPress Beta Tester plugin
  • 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/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 9.2 will be published later today (Oct 19) and that is the version that will be merged into WordPress 5.6 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • Gutenberg plugin 9.2 release is scheduled for October 21.

Our reading list for this week:

Contributor Links

Looking forward to ‘seeing’ many of you at the next 🐝 docs Slack meeting on October 26, 2020 at 14:00 UTC

Digital Checking 🐝-Docs team for the week of October 5, 2020

Our Digital Check-in for this week:
Please share the following in the comments:

  • What did you work on last week?
  • What would you like to work on this week?
  • What are your blockers (things that stand in your way of your work) ?

Our reading list for this week:

Contributor Links

Looking forward to ‘seeing’ many of you at the next 🐝 docs Slack meeting on October 12, 2020 at 14:00 UTC

Digital check-in for Block-editor end user documentation (🐝 docs) team (9/21/2020)

Our Digital Check-in for this week:
Please share the following in the comments:

  • What did you work on last week?
  • What would you like to work on this week?
  • What are your blockers (things that stand in your way of your work) ?

Links

Looking forward to ‘seeing’ many of you at the next 🐝 docs 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 on September 28, 2020 at 14:00 UTC

Agenda for Docs Team Meeting September 14, 2020

When: Monday, September 14, 2020, 15:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

  1. Attendance
  2. Meeting Note-taker & Facilitator for next week’s meeting
  3. Project Updates
  4. External Linking Policy
  5. Docs Videos
  6. New Member Mentoring
  7. Monthly Coffee Break Reminder (September 2020)
  8. Google Season of Docs 2020 Updates
  9. Open Floor

#agenda, #meetings

Digital check-in for Block-editor end user documentation (🐝 docs) team

After a series of weekly chat meetings 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/. channel #meta-helphub, we are testing “digital check-ins” for information and task coordination in September. Chat meetings will only take place every other week. 

For new contributors, here is the outline and all the links necessary: Getting started as a new contributors.

The Google sheet also has an “Experienced Contributors” tab and gives us an overview of what people are editing and what is on our priority list.

The source of truth for our ongoing work is the Trello board with the columns “Need changes /New Pages” and “Work in Progress”.

A few meetings ago I outlined a possible workflow for experienced contributors in slack and I will publish it on the make blog later this week as proposal with a request for input. 

The next Slack-chat meeting for 🐝-docs team will be September 14 at 14:00 UTC in the #meta-helphub channel. Feel free to post questions and comments between meeting there as well.

And now for our Digital Check-in for this week:
Please share the following in the comments:

  • What did you work on last week?
  • What would you like to work on this week?
  • What are your blockers (things that stand in your way of your work) ?

Season of Docs 2020 Projects Move Forward

Google recently announced that two of our Season of Docs 2020 projects are moving forward:

  • Documentation Style Guide proposed by Jon Ang (@kenshino)
  • Improving Article Discovery proposed by Estela Rueda (@estelaris)

These were two of nine possible Docs team projects proposed to GSOD technical writers for vetting.

We arrive at this happy moment after four months of ongoing process and collaboration. Considering there were 49 other organizations participating in Google Season of Docs 2020, it’s a credit to our community effort to bring dedicated technical writers to both projects.

Docs team contributor Atharva Dhekne (@tacitonic) is the technical writer for the Documentation Style Guide project. Milana Cap (@milana_cap) and Felipe Elia (@felipeelia) will be the project mentors.

For Improving Article Discovery, we welcome Diana Mivelli (@dmivelli) as the project’s technical writer. Project author Estela Rueda and (author of this post) Tim O’Haver (@timohaver) will be the project mentors.

Near term, the Season of Docs timeline allows for our writers to get acclimated. By middle September, Atharva and Diana will be fully engaged in their documentation work through November.

#season-of-docs

Proposal for #docs Channel Extension

*this is a cumulative doc/proposal from the Docs Onboard Team

Purpose

To create an area away from the high traffic active postings in the main channel that new and existing Contributors can go for assistance and support. Members can also ask a quick question in the new channel. This would declutter the existing #docs channel from error reports and questions, while distinguishing it exclusively for docs related discussions.

The idea is to is to have a combination of:

-On Demand Lists (ie: /newcontributor-tasks, /specific-itemlinks, /handbook-sections)

 *returns info we setup

—>> using Slackbot for the lists

-Live in Channel Support (General Operating/Convention QA, Orientation Hub)

Naming

Some ideas for possible naming convention:

#docs-help

#docs-support

—————————————

Reason

At this point, we’ve been direct messaging people and working with them one on one to get started, but this would allow us to have a hub to do so, while information supplied to others could also be of benefit as reference.

Presently, we’ve noticed (especially in the case of new contributors), they tend to get overwhelmed and also intimidated by asking for information in the channel.  We’re also duplicating quite a bit of human effort in the case where we have potential solutions to make this process more efficient.