Agenda for Docs Team Meeting November 30, 2020

The next meeting is scheduled with the following details:

When: Monday, November 30, 2020, 15:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

  1. Project Updates
  2. New Member Mentoring
  3. Monthly Coffee Break
  4. Meeting Times
  5. 2020 Holiday Planning for Docs Team
  6. Google Season of Docs 2020
  7. Discussion: Structure of the Handbooks using flow chart
  8. Open Floor

#agenda, #meetings

Summary for Docs Team Meeting on 23 November 2020

Attendance

@estelaris, @chaion07, @bph, @harishanker, @tacitonic, @veralee, @justinahinon, @paaljoachim, @cguntur

Thanks to @estelaris for facilitating the meeting.

Housekeeping
Project Updates

@bph is planning to do a guided documentation sprint for the BEE-Docs starting this Wednesday through Friday (25 to 28 November). The extensive list of the changes in WordPress 5.6 that needs to be triaged and categorized, compared to the current pages and transformed into a contributor task list. Birgit will be online every morning 9 to noon EST. Please join her at your convenience during these times and contribute to BEE-Docs. Birgit will be posting an announcement p2 later on.

@justinahinon is collaborating with @paaljoachim 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/ Developer Documentation in order to improve it. Justin hinted that there might be a bit more progress than the past weeks.

New Member Mentoring

6 new members joined #docs in the week between 16 and 23 November 2020. Thanks to @prubhtej for the information.

Meeting Times

Due to the general confusion with the time-zones a new Doodle was created by @kenshino. Everyone is requested to cast their votes.

Monthly Coffee Break

The November Coffee Break was hosted by @estelaris with 5 participants joining. @chaion07 will be posting a summary in a p2 later on.

Google Season of Docs 2020

@tacitonic is reported the following:

@estelaris mentioned that the classification project will start reviewing 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. articles and coordinate with the BEE-docs team to figure out how to move forward.

The GSoD team would love to hear from the Docs team on the Do’s and Dont’s including comments related to the Style and Tone section.

Open Floor

@bph informed everyone that we need to enable discussion per page since the feedback section that’s now available on HelpHub. Users will be able to leave comments for the Admins and Moderators to be able to view them using wp-admin. Also in the works is a way to revise an article without taking the existing page offline or update unfinished. We will be able to work on revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. and then schedule making them public.

@paaljoachim asked if there been any talk about going through the structure of the handbooks and suggested that creating a flow chart of how docs are linked together can help improve on the user experience. @estelaris mentioned that there has been discussion on this in the past and advised everyone that any idea or a proposal on the topic is welcome. Paal will be bringing this topic next week since majority of the team is unavailable for this meeting.

#meeting-notes, #meetings, #summary

Summary for Docs Team Meeting on 09 November 2020

Attendance

@crs1138, @chaion07, @leogermani, @atachibana, @tacitonic, @stefanocassone, @justinahinon, @veralee, @crstauf, @kafleg, @harishanker, @FahimMurshed, @sukafia, @mehbubrashid, @estelaris, @kenshino

Thanks to @leogermani for facilitating the meeting.

Housekeeping
Project Updates

MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. from Codex to Code Reference: @stevenlinkx and @collinsmbaka continued migrating and re-routing 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. 124 of 355 (34.9% < – 30.4%). @atachibana edited each method of information of the class references. @dd32 added a redirect to every page. No change in 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 handbook until the external linking and the obsolete docs gets resolved.

Meeting Times

Due to the general confusion with the time-zones on the current Doodle, @kenshino will create a new Doodle and @crs1138 will notify all contributors who already voted on the original Doodle about the need to vote again.

New Member Mentoring

There are 5 new members joining #docs in the week between 2 and 9 November 2020.

Monthly coffee break (November 2020)

@estelaris will run the next monthly coffee break which will be on the Thursday 19 November 2020. The time for the coffee break should be Asia friendly and will be specified later on.

Google Season of Docs 2020

@tacitonic is currently working on the Punctuation section and updates the progress in the README file on the daily bases.

@dmivelli has finished reviewing the discoverability project and submitted a long list of typos and grammar errors that @estelaris will be fixing this week. There are also many titles that must be changed.

Docs Handbook and facilitating collaboration

@leogermani and @themiked rewrote a couple of pages but there is still more work to be done. As an example @leogermani pointed out the Projects page that could reflect more precisely what’s going on in their team. They also worked on the Workflow page. @leogermani suggests an idea to add a “report an issue” button to the pages to make it easier for people who want to collaborate to find their way.

@estelaris confirmed that this kind of button will be part of the new design of the articles template.

@themiked will add a link to the Reporting an issue page to the bottom of every plugin handbook page.

Deprecated Links

@themiked wrote down a document regarding the deprecated links and is asking for some feedback.

#meeting-notes, #meetings, #summary

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

Summary for Docs Team Meeting on 02 November 2020

Attendance

@chaion07 @atachibana @veralee @softservenet @harishanker @leogermani @kafleg @hellofromtonya @FahimMurshed @crstauf @kenshino @tacitonic @estelaris

Thanks to @chaion07 for facilitating the meeting.

Housekeeping
Project Updates

@bph posted an update asynchronous to the meeting.

  • The team will be working on the “Sprint for BEE-docs” during November 25 – 27, 2020. Details will follow. If interested, please leave a comment on the digital check-in post.

@atachibana informed about adding dropped information of Codex to code Reference and re-routing:

  • 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.: 108 of 355 (30.4% < – 25.4%)
  • He also spoke on editing method information of each class’ references.
  • He also thanked @stevenlinx and @collinsmbaka for their contribution. 

@milana_cap previously published a p2 post on HelpHub.

Meeting Times

The team is still awaiting responses to the Doodle link from everyone for the meeting time as many parts of the world have already begun adjusting to the Daylight Saving Times. Please cast your preferences using the Doodle link.

New Member Mentoring

@tacitonic informed the team that we didn’t have any new member joining #docs this week.

Monthly Coffee Break

7 people joined in the Monthly Coffee Break for October 2020 with an EU-friendly timing. A few snaps from the meeting were shared with the team. Thanks to @sukafia for facilitating it including @tacitonic, @crs1138, @chaion07, @thisisyeasin and others who joined.

The next Coffee Break will take place on the 26th of November (tentative). More info will be shared as we draw closer to the date. 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.” @sukafia or @chaion07 if you require further assistance.

Google Season of Docs

@tacitonic & @diana did not have anything new to add for this week.

@estelaris suggested that a meeting is scheduled for everyone involved in the GSoD project to take part in.

Open Floor

@joyously brought up this question, a few weeks ago: What to do with articles/pages that contain information that is no longer relevant or deprecated

@leogermani suggested adding a deprecation notice at the top of the page and link to relevant up to date content.

@themiked will write a p2 post covering different aspects of the topic discussed.

#meeting-notes, #meetings, #summary

Agenda for Docs Team Meeting November 02, 2020

The next meeting is scheduled with the following details:

When: Monday, November 02, 2020, 15:00 UTC

Where: #docs channel on Slack.

Meeting Agenda

  1. Project Updates
  2. External Linking Policy
  3. Docs Videos
  4. Meeting Times
  5. New Member Mentoring
  6. Monthly Coffee Break Summary (October 2020)
  7. Google Season of Docs 2020
  8. Discussion: What to do with articles/pages that contain information that is no longer relevant or deprecated?
  9. Open Floor

#agenda, #meetings

Agenda for Docs Team Meeting October 19, 2020

The next meeting is scheduled with the following details:

When: Monday, October 19, 2020, 15:00 UTC

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:

  1. Project Updates
  2. External Linking Policy
  3. New Member Mentoring
  4. Monthly Coffee Break Reminder (October 2020)
  5. Google Season of Docs 2020
  6. Meeting Times
  7. Open Floor

#agenda, #meetings

Agenda for Docs Team Meeting September 28, 2020

The next meeting is scheduled with the following details:

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

Where: #docs channel on Slack.

Meeting Agenda

  1. Project Updates
  2. External Linking Policy
  3. Docs Videos
  4. New Member Mentoring
  5. Monthly Coffee Break Update (September 2020)
  6. Google Season of Docs 2020
  7. Open Floor

“Do not allow your fire to go out.Spark by irreplaceable spark in the hopeless swamps of the not-quite, the not-yet, and the not at all. Do not let the hero in your soul perish in lonely frustration for the life you deserved and have never been able to reach. The world you desire can be won. It exists. It is real. It is possible. It is yours.” 

Ayn Rand

#agenda, #meetings

Summary for Docs Team Meeting on 21 September 2020

Attendance

@justinahinon, @dianamivelli, @estelaris, @kartiks16, @tacitonic, @chaion07, @atachibana, @sukafia, @bobbingwide, @kulsumsiddique, @mkaz.

Thanks to @estelaris for Facilitating the Meeting.

Notetaker & Facilitator Selection

Notetaker: We could use a few volunteers to take notes for our weekly meetings. If you want to help then please comment here or let us know during our meetings.

Facilitator for the next meeting: @chaion07

Next Meeting: 28 September 2020

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/..

Project Updates

@milana_cap updated badges page with a new document and a process for tracking contributions. (asynch to the meeting)

@atachibana reported on 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:

  • 29 Classes out 43 have been completed which is an improvement of 7.4% leading to 67.4% from last week’s 60.5%, and
  • 51 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. out of 355 have been completed which is an improvement of 2.6% leading to 14.4% from last week’s 11.8%.
  • @atachibana thanked @stevenlinx for the contribution.
  • He also did some housekeeping on Codex this week and welcomed suggestions from everyone.

@bph also provided an update beforehand on Digital check in 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.-Editor End User Documentation (BEE-docs). Birgit requested that the BEE-docs team members leave comments on that post. (async to the meeting)

Docs Videos

@milana_cap fully recorded a contributing video and forgot to silent nearby devices and as a result there were a lot of background noises in the recording. Eventually had to delete it and she’ll attempt to re-record it. (async to the meeting)

External Linking Policy

@milana_cap reported prior to the meeting that the team started with the Plugin Developer Handbook for the discussion on External Linking Policy. @themiked outlined two phases. Please let Milana know if help is needed with this. We want to make the entire process transparent and publish on our blog. It’ll also help with defining the workflow for the other parts of #docs.

@themiked also reported that the goal is to compile a list of all the links on all the pages in the 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 guide and start with that, hopefully deleting them all and then adding back the ones on the approved domain list (asynch to the meeting).

New Member Mentoring Team

Due to everyone’s commitments, the Mentoring Team isn’t being able to properly focus on the Mentoring process for the past few weeks. The team is looking for new people to join over Making WordPress #docs team.

Please contact @sukafia, @softservenet, @tacitonic or @Prubhtej_9 with your ideas, suggestions and comments (if any).

Monthly Coffee Break Reminder (September 2020)

@sukafia provided the team with the schedule for the Monthly Coffee Break for September 2020.

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.” @sukafia or @chaion07 if you require further assistance.

Google Season of Docs

@tacitonic reported:

  • Working Repository has been transferred to the WordPress organization on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/.
  • Almost done with the first section. You can read more about it here: https://github.com/WordPress/WordPress-Documentation-Style-Guide/tree/master/docs/2-document-guidelines (Overall status: one week ahead of schedule).
  • Waiting for a confirmation from the #docs team for a suitable location for the Style Guide on 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/ for a request that was made on the 15th of September

@dianamivelli reported:

  • Been reading HelpHub topics, making sure the titles are applicable, and suggesting new titles for some.
  • Raised the topic of identifying a consistent title style such as action+object for the title, when possible.
  • Further discussion is being done on a private Slack channel consisting folks from the #docs team that @estelaris had opened.

@estelaris added:

  • The Slack group includes both Technical Writers and all four mentors to discuss any topic that relates to both projects, as we will coincide in certain points and it is good to agree on the best approaches.
  • The big topic discussed this week was ‘Article Titles’. Removing Gerunds and adding an action+object title.
  • Also discussed the use of one-word titles.

The Technical Writers will be following the Handbook Grammar Guide as always. Thanks to @atachibana for sharing the link.

Open Floor

@bobbingwide asked if WordPress documentation could be kept up to date with the latest release? @estelaris answered that it would be really nice and the team is working hard to reach that goal. But since we had to migrate the articles from one site to another, we are taking the time to also update those articles. Another team is working on a new design for the pages. The Google Season of Docs Team is working on a new writing style guide and a new classification to implement a new navigation to documentation. There is also the Release Team who is working on adding documentation on the new releases. Not to mention the typos, broken links, small updates, etc that need constant upkeep.  With too many moving parts the team is working very hard and will reach our goal of having up-to-date, easy to find documentation soon.

@bobbingwide further asked, How committed is the Release Team to delivering the documentation for the new release concurrently with the new release? @joyously advised this question to be addressed in the Dev Chat and the editor in particular should be documented before being incorporated into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

@bobbingwide also asked on the point of view of the docs team? @estelaris replied saying that the Release Team is very committed particularly to work on that and documentation needs to be ready before the public release.@mkaz added by saying there shouldn’t be a #docs team, that function should be a part of every feature development and those features shouldn’t be merged/released without documentation. @estelaris also shared the link to the 2020 WordPress Release Squad and another link to the WordPress 5.6 Release Planning @makz added by saying that it should be more integrated into the development of the features- if something doesn’t get merged without documentation, then you wouldn’t need a documentation squad for the release, by default it would be there.@justinahinon added async to the meeting by saying that one of the roles of the Release Documentation Team is to ensure that new things that come in the release receive proper documentation. So approximately 90% (estimation), new stuff in a release are documented by the date of the release. @estelaris invited @bobbingwide to attend the Dev Chats in the #core channel on Wednesdays at 8 PM UTC. @themiked added by saying that this may not be a priority for the Dev Team as there should be a docs representative for every release.

@tomjn asked if there is a document for how to contribute to docs that has all the things? @estelaris shared a link to the Docs Handbook. @mkaz also shared a link to the Block Editor Handbook. @jouisly suggested that the Handbook should be easier to discover.

@milana_cap suggested that we should make a list of the musicians in our team. She also shared her list and requested others who can play an instrument or into music to comment in this post.

#meeting-notes, #meetings

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