Milana Cap 9:50 am on February 4, 2021
Tags: q1, q1-2021   

Team Goals for Quarter 1, 2021

Biggest challenges from previous periods:

  • Slow processes, mainly in making decisions, even with simple things.
  • Lack of response from other contributors (e.g. commenting on p2 posts)

This post should serve as a rough (or not so rough) focus plan and set of goals for the Docs team in the first quarter of 2021.

Content team

@atachibana – Contents migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. team will complete the task (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. and classes migration) within a Q1.

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

@bph – 

  • We are triaging 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/ Changelogs 9.3 – 9.9 for End-User relevant changes in “Features” and “Enhancements” coming to 5.7
  • Beginning of February – A team sprint to prepare next set of tasks
  • Replace “More Options” section with link to “More Options”-page
  • Outline of Full-Site-Editing documentation for 5.8
  • Ongoing recruiting and onboarding of new contributors
  • Team checking on current workload. 
  • Fielding Feedback from readers. 

Design team

@estelaris – design proposal:

  • 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/. new reqs – week 4
  • p2 new classification – week 6
  • p2 on final navigation – week 8
  • p2 on templates draft – week 10
  • p2 proposal new design for documentation – week 13

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 Developer Handbook

@themiked – Based on the discussion here (1), the Plugin handbook will develop a way to indicate obsolete docs on both a page-level and a section-level. This will be done with an eye towards it being used elsewhere.

The modernization of the handbook is ¼ of the way done. There are four primary steps in this process:

  1. Convert content to blocks – done
  2. Edit content for clarity and consistency of tone
  3. Confirm that every code snippet conforms to best practices (phpcsPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS., phpcbf, proper naming, good use of comments, and that it actually does what it says it does)
  4. Revisit of the writing to conform to the style guide, whenever that is finished.

(1) What to do with old/obsolete documentation – Make WordPress Documentation 

Block Editor Handbook

@justinahinon – improving the structure of the block editor handbook: https://make.wordpress.org/docs/2020/08/13/plan-proposal-for-a-new-better-structured-gutenberg-developer-documentation/

Plan

  • Improve the structure and the design of the homepage – done
  • Reorganize the handbook table of content (in progress – https://github.com/WordPress/gutenberg/issues/28460)
  • Find a place for FSE documentation
  • Overall, add design improvements were needed in the handbook

Keep up with Gutenberg: https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/ 

More Info (DevHub)

@juliobox – 

User Notes (DevHub)

@audrasjb, @crstauf – stay on top of pending user notes: check regularly and optimize process for handling feedback for doc changes.

They also regularly open TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets when the comments raise issues located in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. docblocks.

Common APIs Handbook

@leogermani – 

External Linking Policy

@themiked, @milana_cap – Finish first and the second phase of reviewing Plugin Developer Handbook: https://make.wordpress.org/docs/2020/12/01/external-linking-policy-1st-review-of-plugin-developer-handbook/ 

Documentation Handbook

This project was neglected in the past quarter. We should make some time to review it and pinpoint spots that need updating.

Contributing Videos

After having two videos published we neglected this project as well. Perhaps we could plan for a couple of more in this quarter.

Google Season of Docs

@tacitonic 

  • Finalize and complete the Style Guide by March 1, 2021.
  • Write the project report.
  • Parse the 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/ repo to make.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//docs/style
  • Initial public release of the Style Guide.

Onboarding New Members

@sukafia

  • Set up an 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.
  • Add the mentorship team to the handbook
  • Call word for mentorship (a word people can use in the slack channel that automatically 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.” members of the team)

HelpHub Localisation

Locales updates

@audrasjb: the French Documentation Team nominated two team leads (@jdy68 and @chaton666) and we’re now at 50% of coverage. In early 2021, we started to create our own original contents.

#q1, #q1-2021

ashiquzzaman 10:02 am on April 18, 2021
Tags: meeting-agenda   

Agenda for Docs Team Meeting April 19, 2021

The next meeting for the Make WordPress Global Documentation Team is scheduled with the following details:

When: Monday, April 19, 2021, 14:00 UTC

Where: #docs channel on Slack.

Meeting Agenda:

  1. Project Updates
  2. Team goals updates
  3. New Member Mentoring
  4. Google Season of Docs
  5. Unified Doc License page
  6. Author attribution to docs
  7. April Coffee Break
  8. Discussion about the process gap between dev notes release stage and docs team writing about a feature, review last weeks’ discussion
  9. Open Floor/Q&A

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

Thank you!

#agenda, #meetings

#meeting-agenda

ashiquzzaman 7:24 am on April 13, 2021
Tags:   

Summary for Docs Team Meeting April 12 2021

Attendance: @crstauf, @chaion07 , @tacitonic , @justinahinon , @FahimMurshed , @atachibana , @estelaris , @bph , @stefanocassone , @themiked, @ashiquzzaman

Housekeeping:

Where: #docs channel on Slack.
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/..
When: Monday, 12 April 2021, 20:00 GMT+6
Meeting Facilitator: @tacitonic
Meeting Note Taker: @ashiquzzaman
Next Meeting: Monday, April 19, 2021, 08:00 PM GMT+6

Project Updates:

From @tacitonic For the Style Guide:
Priority: Completing the last remaining section.
Challenge: Parser inconsistencies.
Big Win: Style Guide was published.
For the Style Guide, @tacitonic completed 20/28 articles in the last section.

From @themiked 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
Priority: 
1. Applying an external linking policy to pages as appropriate  
2. Picking a single page and applying a style guide to it
Challenge: not losing my mind in syntactic pedagogy
Big Win: the above

@tacitonic inquired about whether the external linking policy finalised, because external linking articles in the style guide are on hold for that.

To which themiked replied – Partial implementation has been done.

@bph no updates

From @justinahinon: For the restructuring of 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 handbook:
Priority (for next quarter): Continue iterating on the current documentation
Challenge: The fact that the doc is synced 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/ and parsed sometimes leads to challenges (redirections, syncing errors, live updates, etc..)
Big Win: The initial restructuring plan was completed.


Team goals updates:

Q1 team goals updates:

@zzap requesting all project reps to visit the – Team goals for Quarter 1, 2021 post and report progress in the format:

Priority (for next quarter): 
Challenge: 
Big Win:

Google Season of Docs

The team is waiting for Google’s announce of selected projets, which is planned for next Friday.

In the meantime, the comments are still open on the projects ideas list https://make.wordpress.org/docs/2021/03/26/google-season-of-docs-2021-project-ideas-list/


Open Floor

@justinahinon shared tasks French WordPress documentation team is working on, that can be useful for EN docs team – 

the French WordPress documentation team has been working on something really interesting in relation to the user documentation of the editor blocks.

Instead of rewriting the description and functioning of the common options for each block, the French Doc team created pages for those parts which are then reused in the block articles.

For example, block options like advanced settings, typography, colors and parts of the block toolbar are shared by all blocks. Having their docs separate makes it easier to maintain them, and not have to make changes to a dozen or so articles when there is a change in the editor.

@audrasjb made a screenshot with annotations to show how it works.

This is led by @jdy68 and @chaton666

#meeting-notes, #meetings, #summary

#meeting-notes

#meeting-notes

ashiquzzaman 5:41 pm on April 5, 2021
Tags:   

Summary for Docs Team Meeting April 05 2021

Attendance

@estelaris , @chaion07 , @atachibana ,@tacitonic ,@crstauf , @ashiquzzaman

Housekeeping

Project Updates

No updates from the content side

New Member Mentoring

n/a

Google Season of Docs

@tacitonic completed 20/28 articles for the Word List. 

For this year’s GSoD, the WordPress doc team has to wait till April 16, to know if WordPress is selected as an org this year.

Open Floor/Q&A

@estelaris mentioned that during the project updates, there is a new post about the revision of documentation article is part of the Help Hub redesign series,

#meetings #meeting-notes

Estela Rueda 1:40 pm on April 5, 2021  

Update on the revision of documentation

This article is part of the Help Hub redesign series. Previous articles on this project at listed at the bottom.

As previously established, the Help Hub articles have problematic navigation as they are now. There are numerous reasons why that has happened but the new plan focuses on better use of categories.

As of now, there are 9 main categories and some articles have 2 or more categories making the navigation confusing. Another issue is that the landing page does not contain a table of contents per se, instead shows links to some articles.

The plan is to create 4 pillars and add categories to each pillar. Because this work is not done, there will be another post with more details. Let’s talk about the articles.

The proposal for a new navigation includes reading, reviewing, and classifying each one of the 170+ articles on Help Hub plus the articles for 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.

What are we reviewing?

  • Content: what is the article about? wherein the website creation does it fall into?
  • Codex links: are links still directing to a Codex page? does that Codex page still exists or has been migrated (without updating the link)?
  • Information: is the feature/process/tool described/recommended still valid or are they outdated?
  • External links: are links up-to-date or are they too old? is the link directing to a 404? flag all external links for docs team review.
  • Structure: are there too many links in the same paragraph? is the article following the new style guide (wording, headlines, punctuation, etc.)
  • Code snippets: are they well structured? is the code complete? are they needed?
  • Images: is it a good example? is it the latest version?

We feel that the revision is not exhaustive, but we will be as detailed as time and resources allow it. The work is being tracked on a spreadsheet because it needs to be reviewed by different contributors:

The process

The revision of articles began as a project under the 2020 Google Season of Docs. The assessment done by the GSoD technical writer included title changes and suggestions of merging/deleting pages with repeated or similar content. @dmivelli also came up with a first navigation proposal.

As a designer, I am reading each article to understand the documentation structure and can propose logical navigation, and at the same time, making recommendations on outdated content, structure, flag links, and image updates.

@atachibana from the documentation team is commenting on my recommendations, finding new links to replace flagged links and revisiting outdated content.

We still need the review of a developer to check on the code snippets and other technical information we are not familiar with.

Before making any updates to the articles, the documentation team will have a chance to have a final assessment.

We are working as fast as we can, but we need help with reviewing. If you are interested in helping to review articles and giving your recommendations, please reach out to @estelaris on the #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/. channel.

Previous articles

Props to @zzap and @atachibana for post edits.

Estela Rueda 1:00 pm on April 5, 2021  

Agenda for Docs Team Meeting April 5, 2021

The next meeting for the Make WordPress Global Documentation Team is scheduled with the following details:

When: Monday, April 5, 2021, 04:00 PM GMT+2

Where: #docs channel on Slack.

Meeting Agenda:

  1. Project Updates
  2. New Member Mentoring
  3. Google Season of Docs
  4. Discussion about the process gap between dev notes release stage and docs team writing about a feature, review last weeks’ discussion
  5. Open Floor/Q&A

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

Thank you!

#agenda, #meetings

Akira Tachibana 1:00 pm on April 2, 2021  

Summary for Docs Team Meeting March 29, 2021

Attendance

@kenshino, @atachibana, @mkaz, @chaion07, @tacitonic, @noyeomhou, @estelaris, @deadpool76, @themiked, @milana_cap, @justinahinon, @timothyblynjacobs

Housekeeping

Monday, April 5, 2021, 14:00 UTC

Project Updates

@estelaris is updating and reviewing 170+ articles. She is making some suggestions and flagging links (404s, old content, etc). Last week, she asked the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team if we could get some help, still waiting on someone from the French docs team to reach out. Also, she has to follow up with the support team to see who can help reviewing articles (links and content). She will write up a 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/.  on the update of the docs review we are doing.
@estelaris signed up for the quarter update call with Matt and Josepha.

No update for 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 developer handbook.

@tacitonic had completed  19/28 articles in the Word list and usage dictionary for the Style Guide. Also he wrote a report for the project. Already the hosting team reached out to apply the Style Guide to their handbook. 

Ratifying additional team leads

@kenshino wrote the article to recommend that @milana_cap and @atachibana to the Doc Team Leads with him for a “more hands make light work” approach. There’s no objection and approved.

Full Site Editing Documentation

@estelaris will consider FSE as a new categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. of HelpHub restructuring and build it in the proposal.

@tacitonic suggested that FSE docs could be implemented as a Season of Docs project if possible.

@themiked suggested that dev notes release stage is too late. @kenshino wants to suggest a way to fill in the process gap. We might talk more about this in the next meeting. @estelaris suggested that we write end user documentation at the same time as dev notes are being developed. She will ask in core if we can try this out and see if she can write at least one article for end user doc.

New Member Mentoring

@tacitonic reported that we have 7 new members joining the #docs team since 22 March 2021. Please join me in welcoming
@jahidulhassan, @Cynthia Peter, @Keith L, @Javid Hussain, @deborahtrez12, @Nikema Prophet, & @chraebs.

Google Season Docs

@justinahinon posted last week –

Already, those projects were submitted, but we can still edit the project list post and add/remove projects as needed. @justinahinon will explore it if there are any that should be lower priority or any that we missed.

Open Floor

@themiked said “I was doing some work on the weekend and long story short it appears that is_admin() will not only return true when viewing an admin page12:07if you are editing a BG page for example, it will return true at least once, but will also return false multiple times”.
… and, follow the discussion.

#meeting-notes, #meetings, #summary

ashiquzzaman 9:53 am on March 26, 2021
Tags:   

Agenda for Docs Team Meeting March 29, 2021

The next meeting for the Make WordPress Global Documentation Team is scheduled with the following details:

When: Monday, March 29, 2021, 14:00 UTC

Where: #docs channel on Slack.

Meeting Agenda:

  1. Project Updates
  2. Ratify additional team leads
  3. Full Site Editing Documentation
  4. New Member Mentoring
  5. Unified Doc License page
  6. Author attribution to docs
  7. Google Season of Docs
  8. Open Floor/Q&A

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

Thank you!

#agenda, #meetings

#agenda

Justin Ahinon 7:36 am on March 26, 2021
Tags:   

Google Season of Docs 2021 – Project ideas list

Note:

Our application was not accepted for this edition of the Season of Docs. I received the email from Google on Friday, April 16th notifying me of this.

However, the projects we submitted will be highly beneficial to the documentation team, and to WordPress in general. So I’m very interested in leading/working on some of them, and also in supporting contributors who would like to do the same.

In the next few days, I’ll get in touch with the people who were interested in participating in this Season of Docs, and, if they are still interested, see how we can move forward.

Below is a list of projects presented by WordPress for Google Season of Docs 2021. Prospective technical writers can also suggest new project ideas in the comments section.

People involved:

Project list

Project one: @justinahinon

Project name: Create a system to track updates and suggestions to the WordPress documentation

Project description

The problem: The WordPress documentation is huge and divided into multiple sections. There is user documentation and developer documentation of different projects (themes, plugins, block editor, APIs, etc.).

All this documentation is subject to frequent changes as the projects to which they belong evolve. So we end up with requests for changes, requests for updates that are frequently reported on various channels: Slack, Meta Trac, GitHub, etc.

The fact that we don’t have a unified system for change requests and documentation updates makes collaboration difficult; and can be an obstacle for new contributors who want to start with documentation contribution.

So, WordPress really needs to have a unified tracking system so that we can track these requests and the work to fulfill such requests. And we need to create a process to utilize this system properly.

Measuring the project’s success

The main indicator of success is the effective implementation of a system and process to report documentation that is obsolete, needs to be updated or corrected.

The second indicator of success is the use by contributors of the system and process implemented.

Required skills

The technical writer who will work on this project should have an idea of WordPress documentation, how they work, and how the documentation team maintains them.

The technical writer will have a mentor with experience on the documentation team, who can provide assistance and guidance as needed.

Project two: @chaion07

Project name: Documentation for a better on-boarding experience: Supporting new contributors to WordPress

Project description

The problem: Reported by W3Techs WordPress currently powers over 40% of the web. The WordPress Org comprises of contributors and the number is growing by the day. With 18 Make WordPress Teams it can be a daunting experience for new contributors in finding their place. Many teams have their on-boarding documentations as part of the Handbook. Some are automated, for example the core team while others lack enough clarity for new contributors to understand.

Thus, WordPress should include both technical and other know-how documentation for contributors. Season of Docs is the perfect excuse to improve each of the 18 teams’ handbooks emphasizing on the contributor on-boarding experience.

This project aims to improve the documentation of the on-boarding experience for contributors. With rich, interactive content including multilingual videos, the goal is to support the existing documentation from individual team’s handbooks and to standardize them in a way that can be truly beneficial for the contributors.

Measuring the project’s success

Adding relevant section to the handbooks and those pages would be the main success criteria for the project. Being able to include localized content can also help improve the overall user experience and reach a wider audience.

An additional success criteria for the project can also be on the use of the content and in the implementation of the content when put to the test.

Required skills

The technical writer should have an understanding on the following:

  • How Make WordPress Teams function
  • Weekly Meetings and Triage Sessions
  • Workflow of the Make WordPress Teams
  • How to propose changes for the Handbook
  • How WordPress is being improved (release process)
  • Where to ask for help and how to avail them
  • Identifying the contact person for each Make WordPress Teams

The technical writer can have a mentor with experience on the documentation team, who can provide assistance and guidance if needed.

Related Material

Project three: @tacitonic

Project name: Write Gutenberg block editor end-user documentation

Description

There are gaps in the existing documentation for the Gutenberg block editor with missing pages and existing pages that need to be updated – as 80% of them haven’t seen an update since WordPress 5.0 came out. With constant UI changes on for every version, Gutenberg block editor documentation is evolving rapidly with new version releases.

Required skills

A content creator’s (blogger, writer) understanding for the block editor; no development skills are required.

Related material

Project four: @tacitonic

Project name: Improve existing user and developer documentation and handbooks

Description

We have a lot of developer documentation. WP Core’s documentation is mostly automated. However handbooks that describe how one would create a theme, make a plugin, use the REST API, or automate things via the CLI do not receive updated documentation. In turn, this requires that all handbook maintainers know all the changes in each core release to be able to write something useful.

In some cases, the handbooks are updated but don’t provide enough examples for new developers to get started. We would like to close these gaps.

Another improvement would be to adopt the newly published WordPress Documentation Style Guide for existing documentation.

Related material

Project five: @mkaz

Project Name: Extending block editor developer documentation

Description

Documentation on developing on top of block editor is, depending on the topic, either scarce, outdated, or non-existent. Considering that the block editor is a significant language leap for WordPress developers, the project itself would benefit from having detailed documentation in a form of guides or tutorials, on how to utilize and extend core functionality and what the best practices are.

Related material

Additional information

  • Previous participation in Season of Docs, Google Summer of Code or others:
    WordPress participated in Google Season of Docs 2020. WordPress was also a mentoring organization for Google Summer of Code 2014.

#season-of-docs-2021

ashiquzzaman 2:29 am on March 23, 2021
Tags:   

Summary for Docs Team Meeting on March 22, 2021

Attendance

@crstauf ,@mazharul , @chaion07 ,@ashiquzzaman ,@justinahinon ,@tacitonic ,@atachiba ,@estelarisestelaris ,@noyeomhou ,@habib919000

Housekeeping

Project Updates

For the contents side, there are no updates for now. @atachibana will fix the check logs issues.

@estelaris is working on reviewing the list of articles. She is also have a 15 min call with matt & Josepha during Q2 Listening Hours to discuss about making documentation better

@tacitonic update from Style Guide project:

Google Season Docs

@justinahinon posted last week –

The doc team has 2 people who are interested in mentoring and no project ideas yet. The doc team is requesting to comment on the posts if anyone has any project idea. Also, the team is coordinating everything about the program on this 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/ repo. The deadline for organizations is March 26 and project ideas are required for the proposal.

@estelaris suggested to review the projects that were proposed last year.

New Member Mentoring

We have 11 new members joining the #docs team since 08 March 2021. Please join me in welcoming
@Apostolos Kourmatzoglou, @Sandip Mondal, @EddAllen, @Shahin Sid, @Sagar B, @Maya Shlayen, @rodrigo, @Laurence Bahiirwa, @Alyssa, @Kerin Khan, @Danielle Gaither

Open Floor

n/a

#meeting-notes, #meetings, #summary

#meeting-notes

Akira Tachibana 7:13 am on March 22, 2021  

Summary for Docs Team Meeting on March 15, 2021

Attendance

@chaion07 @habib919000 @justinahinon @tacitonic @stefanocassone @atachibana @estelaris @reachmazharul @crstauf @themiked @ashiquzzaman

Project Updates

@atachibana migrated WordPress Versions page into HelpHub and modifying the contents and links of all changelog.
https://wordpress.org/support/article/wordpress-versions/

@justinahinon made two updates:

  • First, wrapped up last week with the Gutenberg developer handbook reorg (https://make.wordpress.org/core/2021/03/12/block-editor-handbook-restructuring-project-update-march-12/)
  • And posted this (https://make.wordpress.org/docs/2021/03/15/wordpress-is-applying-to-season-of-docs-2021/), about WordPress application to 2021 Google Season of Docs

@themiked
When the style guide is 100% complete, will be taking a page from it and updating 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 using the guide

@tacitonic
‘For Season of Docs, today is officially the last day of the doc development phase. All successful long running projects would be announced today, and hopefully ours would be in there.’

Please refer this great post:
https://make.wordpress.org/docs/2021/03/07/wordpress-documentation-style-guide-google-season-of-docs-2020-project-report-tacitonic/