Title: Make WordPress Documentation – Page 4 – Making WordPress Docs

---

 [  ](https://profiles.wordpress.org/awetz583/) [Andrea Roenning](https://profiles.wordpress.org/awetz583/)
2:58 pm _on_ March 10, 2026     
Tags: [docs ( 158 )](https://make.wordpress.org/docs/tag/docs/),
[meeting ( 26 )](https://make.wordpress.org/docs/tag/meeting/), [summary ( 156 )](https://make.wordpress.org/docs/tag/summary/)

# 󠀁[Documentation team meeting notes – March 10, 2026](https://make.wordpress.org/docs/2026/03/10/documentation-team-meeting-notes-march-10-2026/)󠁿

**Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
+ Video call
**When:** [Tuesday, March 10, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260310T1400)**
Meeting Facilitator:** [@estelaris](https://profiles.wordpress.org/estelaris/)**
Note Taker:** [@awetz583](https://profiles.wordpress.org/awetz583/)

# Next Meetings

### Discussion Meeting

**Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack
**
When:** [Tuesday, March 17 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260317T1400)

### 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/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿

**Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack
+ Video call
**When**: [Tuesday, March 24 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260324T1400)

[View upcoming dates on the Documentation Team meeting calendar.](https://make.wordpress.org/meetings/#docs)

## Open Floor

 * [@parinpanjari](https://profiles.wordpress.org/parinpanjari/) discussed updating
   an image for [Get Started with WordPress](https://wordpress.org/documentation/article/get-started-with-wordpress/)
   documentation
 * [@estelaris](https://profiles.wordpress.org/estelaris/) and [@awetz583](https://profiles.wordpress.org/awetz583/)
   discussed documentation ready for review in the [Blocks articles overhaul project board](https://github.com/orgs/WordPress/projects/267)

[#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/),
[#summary](https://make.wordpress.org/docs/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F03%2F10%2Fdocumentation-team-meeting-notes-march-10-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/awetz583/) [Andrea Roenning](https://profiles.wordpress.org/awetz583/)
6:29 pm _on_ March 3, 2026     
Tags: [docs ( 158 )](https://make.wordpress.org/docs/tag/docs/),
[meeting ( 26 )](https://make.wordpress.org/docs/tag/meeting/), [summary ( 156 )](https://make.wordpress.org/docs/tag/summary/)

# 󠀁[Documentation team meeting notes – March 3, 2026](https://make.wordpress.org/docs/2026/03/03/documentation-team-meeting-notes-march-3-2026/)󠁿

**Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
**
When:** [Tuesday, March 3, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260303T1400)**
Meeting Facilitator:** [@milana_cap](https://profiles.wordpress.org/milana_cap/)**
Note Taker:** [@awetz583](https://profiles.wordpress.org/awetz583/)Find the complete
meeting [on Slack](https://wordpress.slack.com/archives/C02RP4WU5/p1772546760576869).

# Next Meetings

### Discussion Meeting

**Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack
+ Video call
**When**: [Tuesday, March 10 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260310T1400)**
Facilitator**: [@estelaris](https://profiles.wordpress.org/estelaris/)

### Discussion Meeting

**Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack
**
When:** [Tuesday, March 17 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260317T1400)

[View upcoming dates on the Documentation Team meeting calendar.](https://make.wordpress.org/meetings/#docs)

### Facilitation Resources

Helpful resources for facilitating the meeting and writing the meeting notes.

 * [Non-project roles → **Meeting facilitator**](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#meeting-facilitator)
 * [Facilitating weekly meetings](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/)
   workflow page, including the [writing agenda](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/#writing-agenda)
   section.

## Project Checks: Contributions

 * [@awetz583](https://profiles.wordpress.org/awetz583/) Worked on [Video block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2157),
   [Verse block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2140),
   [Image block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2151),
   and [File block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2155)
   which are ready for review.
 * [@milana_cap](https://profiles.wordpress.org/milana_cap/)
    - Completed and closed [Pullquote block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2138)
      and [List block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2132).
    - Recorded 3 short videos for documenting the 7.0 release and uploaded them 
      to wordpress.tv (these will be available soon.)
    - Created a [Github project for 7.0 Documentation](https://github.com/orgs/WordPress/projects/286),
      added automation with 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 by the repository owner. [https://github.com/](https://github.com/)
      workflow to add issues with 7.0 label automatically and added access to release
      team to the project.
 * [@rollybueno](https://profiles.wordpress.org/rollybueno/) Completing working 
   on 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. overhaul including [Quote block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2133)
   and [Code block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2134).
 * [@supernovia](https://profiles.wordpress.org/supernovia/) [Contribution Pathways is now on Github](https://github.com/WordPress/contributor-handbook/blob/feature/pathways/pathways/index.md)
   and will continue to receive updates.
 * [@parinpanjari](https://profiles.wordpress.org/parinpanjari/) Working on updates
   for [Get started with WP](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2184)
   article.

The team is now **down to 657 open issues**, with [28 issues closed in the past week](https://github.com/WordPress/Documentation-Issue-Tracker/pulse).

## Documenting WordPress 7.0 release

[@estelaris](https://profiles.wordpress.org/estelaris/) proposed changes to the 
WordPress release day workflows, including reversing the order of the WordPress 
Versions page to show the latest version first, removing the Roadmap page from the
team’s responsibilities, and updating the History and “Learn about WordPress origins
and version history” pages. The team discussed the challenges and potential solutions,
including exploring automation and using Contributor Days for manual updates.

## Open Floor

### Reviewing the Documentation Review Process

[@supernovia](https://profiles.wordpress.org/supernovia/) asked the team to review
the [documentation review process](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9qo6qd7g64ww#heading=h.ndba4wg45kgd)
and [@estelaris](https://profiles.wordpress.org/estelaris/) and [@milana_cap](https://profiles.wordpress.org/milana_cap/)
plan to provide feedback.

### Switching to Video Meetings

[@milana_cap](https://profiles.wordpress.org/milana_cap/) proposed switching some
of the team’s meetings to video calls, as video discussions tend to be more productive
than Slack-only meetings. The team decided to add additional video calls to the 
monthly schedule.

#### New schema for docs meetings:

 * 1st in month – Slack chat
 * 2nd in month – Video call
 * 3rd in month – Slack chat
 * 4th in month – 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/](https://make.wordpress.org/)
   There are many teams that people can participate in, each with a different focus.
   [https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)(
   video)
 * 5th in month – Video call

[#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/),
[#summary](https://make.wordpress.org/docs/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F03%2F03%2Fdocumentation-team-meeting-notes-march-3-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/)
8:31 am _on_ March 2, 2026     
Tags: [make.wordpress.org/updates ( 55 )](https://make.wordpress.org/docs/tag/make-wordpress-org-updates/),
[p2-xpost ( 139 )](https://make.wordpress.org/docs/tag/p2-xpost/)   

# 󠀁[X-post: Documentation Team Update – March 2, 2026](https://make.wordpress.org/docs/2026/03/02/xpost-documentation-team-update-march-2-2026/)󠁿

X-comment from [+make.wordpress.org/updates](https://make.wordpress.org/updates/):
Comment on [Documentation Team Update – March 2, 2026](https://make.wordpress.org/updates/2026/03/02/documentation-team-update-march-2-2026/#comment-7055)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F03%2F02%2Fxpost-documentation-team-update-march-2-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/)
6:37 pm _on_ February 25, 2026     
Tags: [docs ( 158 )](https://make.wordpress.org/docs/tag/docs/),
[meeting ( 26 )](https://make.wordpress.org/docs/tag/meeting/), [summary ( 156 )](https://make.wordpress.org/docs/tag/summary/)

# 󠀁[Documentation team meeting notes – February 24, 2026](https://make.wordpress.org/docs/2026/02/25/documentation-team-meeting-notes-february-24-2026/)󠁿

**Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
**
When:** [Tuesday, February 24 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260224T1400)**
Meeting Facilitator:** [@supernovia](https://profiles.wordpress.org/supernovia/)**
Note Taker:** [@milana_cap](https://profiles.wordpress.org/milana_cap/)Find the 
complete meeting [on Slack](https://wordpress.slack.com/archives/C02RP4WU5/p1771941622625369).

# Next Meetings

### Discussion Meeting

**Where:** [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack
**
When:** [Tuesday, March 3 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260303T1400)**
Facilitator:** [@supernovia](https://profiles.wordpress.org/supernovia/)**Note Taker:**
[@azharderaiya](https://profiles.wordpress.org/azharderaiya/)

### Discussion Meeting

**Where**: [#docs](https://wordpress.slack.com/archives/C02RP4WU5) channel on Slack
**
When**: [Tuesday, March 10 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260310T1400)**
Facilitator**: [@estelaris](https://profiles.wordpress.org/estelaris/)

### Facilitation Resources

Helpful resources for facilitating the meeting and writing the meeting notes.

 * [Non-project roles → **Meeting facilitator**](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#meeting-facilitator)
 * [Facilitating weekly meetings](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/)
   workflow page, including the [writing agenda](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/#writing-agenda)
   section.

## Project Checks: Contributions

 * [@milana_cap](https://profiles.wordpress.org/milana_cap/)**:** Almost done with
   issue [#2138](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2138)(
   recording video is remaining). Plans to complete another issue this week.
 * [@awetz583](https://profiles.wordpress.org/awetz583/): Worked on [Details block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2135)
   and [Table block](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2139),
   which are ready for review.

The team is now **down to 683 open issues**, with [5 issues closed in the past week](https://github.com/WordPress/Documentation-Issue-Tracker/pulse).

## WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. 󠀁[Learn more](https://central.wordcamp.org/about/)󠁿. Asia 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/](https://make.wordpress.org/)󠁿 There are many teams that people can participate in, each with a different focus. 󠀁[https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/](https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/)󠁿

The Documentation team is missing the table lead for the WordCamp Asia Contributor
Day. The team [has been discussing](https://wordpress.slack.com/archives/C02RP4WU5/p1771942589577359)
possible leads from the list of registered attendees: [@sagargurnani](https://profiles.wordpress.org/sagargurnani/),
[@anandau14](https://profiles.wordpress.org/anandau14/), as possible table leads,
with help from [@bph](https://profiles.wordpress.org/bph/) and [@clk87](https://profiles.wordpress.org/clk87/).

## Documenting WordPress 7.0 release

With the smaller [release squad](https://make.wordpress.org/core/2026/01/22/announcing-the-wordpress-7-0-release-squad/),
the Docs team has two representatives volunteered to work on updating end-user docs
for 7.0, [@sajib1223](https://profiles.wordpress.org/sajib1223/) and [@milana_cap](https://profiles.wordpress.org/milana_cap/).
The team will follow [instructions](https://docs.google.com/document/d/1SoUds02wiBCjmPJR5xu_GdbnkQfyCGn_spYtugebpcM/edit?tab=t.0)
drafted by [@estelaris](https://profiles.wordpress.org/estelaris/), while working
on this new workflow together with [@annezazu](https://profiles.wordpress.org/annezazu/)
on 6.9 release. In this scenario, [@milana_cap](https://profiles.wordpress.org/milana_cap/)
will act as a mentor due to her experience with working on release docs in previous
releases. As the others expressed the interest, this will be done publicly (in the
[#docs](https://make.wordpress.org/docs/tag/docs/) channel), starting from next 
week.

A very helpful resource is provided by [@annezazu](https://profiles.wordpress.org/annezazu/)
in [the comment](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#comment-48392)
on the planning post for 7.0.

## Open Floor

### Contribution Pathways

[@supernovia](https://profiles.wordpress.org/supernovia/) noted that, by WordCamp
Asia, we should have several contribution pathways ready. These will be moved to
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 by the repository owner. [https://github.com/](https://github.com/)
and available to new contributors at Contributor Day. [@estelaris](https://profiles.wordpress.org/estelaris/)
shared the [general GitHub issue](https://github.com/WordPress/Documentation-Issue-Tracker/issues/1920)
the team uses for Contributor Days.

Previously, [@supernovia](https://profiles.wordpress.org/supernovia/) shared three“
contribution pathway” one-pagers created by [@clk87](https://profiles.wordpress.org/clk87/):

 * **[Reviewing an Issue](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9qo6qd7g64ww)**—
   for more advanced contributors; needs critique and correction before publishing.
 * **[Work on Existing Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.ikn705tefvek)**—
   ready to publish pending final review.
 * **[File High Quality Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9e580h1eicew)**—
   ready to publish pending final review.

**Goals for these guides:**

 * Provide clear, step-by-step entry points for new and existing contributors.
 * Eventually be linked from the [main contribution index](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.398bqf8dq2ro)(
   final location still to be decided).
 * Support a growing pool of **200+ student contributors** looking for ways to contribute,
   with more students coming.

## AI-powered documentation assistant for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks

[@estelaris](https://profiles.wordpress.org/estelaris/) shared the draft about the
[AI-powered documentation assistant for WordPress core blocks (draft)](https://docs.google.com/document/d/14ws7j5r_iiH3b9PNIRrzZiNbxJcsTE8eEOMfklziYyU/edit?usp=sharing)
that she will be working on with the [#core-ai](https://wordpress.slack.com/archives/C08TJ8BPULS)
team, and hopefully will be ready for 7.1 It will be trained to give recommendations
based on existing 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. docs. This is one of the reasons why Overhaul has been pushed for
the block docs to be updated.

Any comments, ideas, questions, and reviews for the draft are welcome. Please, leave
them in the document.

[#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/),
[#summary](https://make.wordpress.org/docs/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F25%2Fdocumentation-team-meeting-notes-february-24-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/dmsnell/) [Dennis Snell](https://profiles.wordpress.org/dmsnell/)
3:49 pm _on_ February 25, 2026     
Tags: [make.wordpress.org/core ( 17 )](https://make.wordpress.org/docs/tag/make-wordpress-org-core/),
[p2-xpost ( 139 )](https://make.wordpress.org/docs/tag/p2-xpost/)   

# 󠀁[X-post: Developer documentation restored.](https://make.wordpress.org/docs/2026/02/25/xpost-developer-documentation-restored/)󠁿

X-comment from [+make.wordpress.org/core](https://make.wordpress.org/core/): Comment
on [Developer documentation restored.](https://make.wordpress.org/core/2026/02/25/developer-documentation-restored/#comment-48420)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F25%2Fxpost-developer-documentation-restored%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/supernovia/) [Velda](https://profiles.wordpress.org/supernovia/)
5:40 am _on_ February 24, 2026     
Tags: [agenda ( 175 )](https://make.wordpress.org/docs/tag/agenda/),
[docs ( 158 )](https://make.wordpress.org/docs/tag/docs/), [meetings ( 169 )](https://make.wordpress.org/docs/tag/meetings/)

# 󠀁[Agenda for Discussion Meeting on February 24, 2026](https://make.wordpress.org/docs/2026/02/24/agenda-for-discussion-meeting-on-february-24-2026/)󠁿

The meeting is scheduled with the following details:

**When**: [Tuesday, February 24, 2026, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260224T1400)

**Where**: [#docs](https://wordpress.slack.com/messages/docs/) channel on [Slack](http://www.slack.com/)

**Agenda:**

 1. Attendance.
 2. Note-taker and facilitator selection for the next docs team meeting.
 3. Project check.
 4. Prepping for 7.0
 5. Open floor.

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

 [#agenda](https://make.wordpress.org/docs/tag/agenda/), [#docs](https://make.wordpress.org/docs/tag/docs/),
[#meetings](https://make.wordpress.org/docs/tag/meetings/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F24%2Fagenda-for-discussion-meeting-on-february-24-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/)
9:57 am _on_ February 23, 2026     
Tags: [make.wordpress.org/updates ( 55 )](https://make.wordpress.org/docs/tag/make-wordpress-org-updates/),
[p2-xpost ( 139 )](https://make.wordpress.org/docs/tag/p2-xpost/)   

# 󠀁[X-post: Documentation Team Update – February 23, 2026](https://make.wordpress.org/docs/2026/02/23/xpost-documentation-team-update-february-23-2026/)󠁿

X-comment from [+make.wordpress.org/updates](https://make.wordpress.org/updates/):
Comment on [Documentation Team Update – February 23, 2026](https://make.wordpress.org/updates/2026/02/23/documentation-team-update-february-23-2026/#comment-7054)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F23%2Fxpost-documentation-team-update-february-23-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/supernovia/) [Velda](https://profiles.wordpress.org/supernovia/)
11:12 pm _on_ February 17, 2026     
Tags: [docs ( 158 )](https://make.wordpress.org/docs/tag/docs/),
[meeting ( 26 )](https://make.wordpress.org/docs/tag/meeting/), [summary ( 156 )](https://make.wordpress.org/docs/tag/summary/)

# 󠀁[Documentation team meeting notes – February 17, 2026](https://make.wordpress.org/docs/2026/02/17/documentation-team-meeting-notes-february-17-2026/)󠁿

**Where:** [#docs](https://make.wordpress.org/docs/tag/docs/) channel on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
**
When:** Tuesday, February 17, 2026 at 14:00 UTC**Meeting Facilitator:** [@sagargurnani](https://profiles.wordpress.org/sagargurnani/)**
Note Taker:** [@supernovia](https://profiles.wordpress.org/supernovia/)Find the 
complete meeting [on Slack](https://wordpress.slack.com/archives/C02RP4WU5/p1771336973646589).

# Next Meetings

### Discussion Meeting

**Where:** [#docs](https://make.wordpress.org/docs/tag/docs/) channel on Slack
**
When:** Tuesday, March 3, 2026 at 14:00 UTC**Facilitator:** [@supernovia](https://profiles.wordpress.org/supernovia/)**
Note Taker:** [@azharderaiya](https://profiles.wordpress.org/azharderaiya/)

### Discussion Meeting

Where: [#docs](https://make.wordpress.org/docs/tag/docs/) channel on Slack
When:
Monday, March 10, 2026 at 14:00 UTC**Facilitator:** [@estelaris](https://profiles.wordpress.org/estelaris/)

### Next Meeting Volunteers & Facilitation Resources

After a request for facilitators and note-takers for the March 3 meeting, [@supernovia](https://profiles.wordpress.org/supernovia/)
agreed to facilitate, and [@azharderaiya](https://profiles.wordpress.org/azharderaiya/)
will take notes. This will be the first time for each of them in these roles, so
[@zzap](https://profiles.wordpress.org/zzap/) shared these guides:

 * [Non-project roles → **Meeting facilitator**](https://make.wordpress.org/docs/handbook/get-involved/team-roles/non-project-roles/#meeting-facilitator)
 * [Facilitating weekly meetings](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/)
   workflow page, including the [writing agenda](https://make.wordpress.org/docs/handbook/workflows/facilitating-weekly-meetings/#writing-agenda)
   section.

[@zzap](https://profiles.wordpress.org/zzap/) also noted that the team **no longer
keeps a roll-call style attendance list** in meeting notes, and [@sagargurnani](https://profiles.wordpress.org/sagargurnani/)
will connect with [@azharderaiya](https://profiles.wordpress.org/azharderaiya/) 
privately to help guide him through the note-taking process.

## Project Checks: Contributions

 * **[@zzap](https://profiles.wordpress.org/zzap/):** Almost done with issue [#2138](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2138)(
   recording video is remaining). Plans to complete another issue this week.
 * **[@awetz583](https://profiles.wordpress.org/awetz583/):** Closed three issues:
   [Classic block (#2141)](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2141),
   [Paragraph block(#2129)](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2129),
   and [Preformatted block (#2137)](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2137)
 * **[@estelaris](https://profiles.wordpress.org/estelaris/):** Closed 40+ issues
   for 6.4 dev notes. All work had been done previously but none of the issues were
   formally closed. Each was reviewed and missing links were added.
 * **[@atachibana](https://profiles.wordpress.org/atachibana/):** Closed 2 issues
   for WordPress 6.2.
 * **`@sajib1223`**: Closed 2 issues and 1 spam issue: [#2186](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2186),
   [#2160](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2160)
 * **[@rollybueno](https://profiles.wordpress.org/rollybueno/):** Closed the [Heading Block Overhaul (#2131](https://github.com/WordPress/Documentation-Issue-Tracker/issues/2131))
   and its sub-tasks, plus 1 spam issue.

The team is now **down to 689 open issues**, with 64 issues closed in the past week
alone. [@zzap](https://profiles.wordpress.org/zzap/) and [@estelaris](https://profiles.wordpress.org/estelaris/)
both thanked everyone for their hard work, with special recognition for those working
on the blocks overhaul.

## Open Floor

### Handling Old & Deprecated Issues

[@estelaris](https://profiles.wordpress.org/estelaris/) raised a question: since
the inventory work is surfacing very old issues (6.3 and older), should issues for
blocks that have already been updated to 6.9 be closed?

**Decision:**

 * **Yes** — close them, referencing the newer issue number where applicable.
 * **Exception:** If a feature was introduced in an old version and was never documented
   in later updates, keep it open.
 * For **deprecated blocks** with broken images from old versions: remove the broken
   image from the article and close the issue with a comment noting 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. was
   deprecated and will no longer be updated. Contributors are encouraged to follow
   this same approach when encountering similar issues.

### WP Credits Program Updates

**Handbook Review by [@rossanatrujillo](https://profiles.wordpress.org/rossanatrujillo/):**
[@estelaris](https://profiles.wordpress.org/estelaris/) shared that [@rossanatrujillo](https://profiles.wordpress.org/rossanatrujillo/),
her mentee from the WP Credits program, is reviewing the Docs handbook in both Spanish
and English and has submitted her first draft for review:

 * [Google Doc — Handbook Review Draft](https://docs.google.com/document/d/1ixhpmZXX_GNAjzbWJyYnknEO64zsRvmgBMG3-DqvFgY/edit?usp=sharing)
 * Anyone is welcome to read and leave notes. The first part is in Spanish, the 
   second in English.
 * The goal is for this review to help update the handbook.

[@estelaris](https://profiles.wordpress.org/estelaris/) expressed appreciation for
the program, noting that mentoring is a mutual learning experience around best approaches,
goals, and reasons behind handbook content.

### Contribution Pathways

[@supernovia](https://profiles.wordpress.org/supernovia/) shared three “contribution
pathway” one-pagers created by [@clk87](https://profiles.wordpress.org/clk87/):

 * **[Reviewing an Issue](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9qo6qd7g64ww)**—
   for more advanced contributors; needs critique and correction before publishing.
 * **[Work on Existing Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.ikn705tefvek)**—
   ready to publish pending final review.
 * **[File High Quality Issues](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.9e580h1eicew)**—
   ready to publish pending final review.

**Goals for these guides:**

 * Provide clear, step-by-step entry points for new and existing contributors.
 * Eventually be linked from the [main contribution index](https://docs.google.com/document/d/1dx47WEb-LptMRbygrvqzP9Qa1Jl1v-v6mZgGbAGjyCc/edit?tab=t.398bqf8dq2ro)(
   final location still to be decided).
 * Support a growing pool of **200+ student contributors** looking for ways to contribute,
   with more students coming.

[@zzap](https://profiles.wordpress.org/zzap/) thanked the team for this work and
plans to review the documents and possibly adapt them for the Docs **gamification**
initiative.

### 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 by the repository owner. 󠀁[https://github.com/](https://github.com/)󠁿 Automations, /assign, and Workflow Improvements

[@awetz583](https://profiles.wordpress.org/awetz583/) reported another instance 
where `/assign` failed to assign an issue in GitHub.

[@zzap](https://profiles.wordpress.org/zzap/) clarified that `/assign` can fail 
when:

 * Someone is already assigned to the issue, **or**
 * The issue has a status label other than “To do.”

All current automations (including `/assign` behaviors) are custom-built by [@zzap](https://profiles.wordpress.org/zzap/).
There are many edge cases that can’t be covered, or are too expensive to run because
GitHub would need to process all issues. The automations are good for getting things
started but need refining and/or re-doing. [@zzap](https://profiles.wordpress.org/zzap/)
expressed openness to revisiting these workflows and [@clk87](https://profiles.wordpress.org/clk87/)
may be able to assist with this effort.

[@supernovia](https://profiles.wordpress.org/supernovia/) raised a related question:
can contributors be **unassigned** if they self-assign and then abandon an issue?

**Current situation:**

 * No automatic unassigning for inactivity.
 * Admins can manually unassign people from issues.
 * If someone uses `/assign` on an already assigned issue, they receive an automated
   notice advising them to contact [@zzap](https://profiles.wordpress.org/zzap/).

#### Review Process

[@supernovia](https://profiles.wordpress.org/supernovia/) asked whether anyone can
review issues, or if a certain status is required first — and whether allowing broader
reviews could help clear the backlog.

 * [@zzap](https://profiles.wordpress.org/zzap/) noted it’s difficult to give a 
   blanket answer; it depends on what is being reviewed and what needs attention.
 * [@estelaris](https://profiles.wordpress.org/estelaris/) confirmed that **anyone
   can review**, and that the team will be reviewing more often now that systems
   are getting back in order.
 * [@supernovia](https://profiles.wordpress.org/supernovia/) suggested the idea 
   of a **preliminary review** step.
 * [@estelaris](https://profiles.wordpress.org/estelaris/) explained that related
   issues are being gathered together, with the goal of updating as much as possible
   up to 6.9 so the team is **ready for 7.0**.

### Action Items

 * For any `/assign` misbehavior, 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.” [@zzap](https://profiles.wordpress.org/zzap/)
   directly.
 * Revisit and possibly redesign current workflows and automations.
 * [@clk87](https://profiles.wordpress.org/clk87/) may be able to help with automation
   improvements.
 * Work through the backlog of abandoned or stalled issues.
 * [@sagargurnani](https://profiles.wordpress.org/sagargurnani/) to connect with
   [@azharderaiya](https://profiles.wordpress.org/azharderaiya/) to guide him through
   note-taking.
 * [@zzap](https://profiles.wordpress.org/zzap/) to review [@clk87](https://profiles.wordpress.org/clk87/)‘
   s contribution pathway documents and explore gamification integration.
 * Team to revisit assignment/abandonment workflows and work through the backlog
   of stalled issues.
 * Anyone interested is welcome to review [@rossanatrujillo](https://profiles.wordpress.org/rossanatrujillo/)‘
   s [handbook draft](https://docs.google.com/document/d/1ixhpmZXX_GNAjzbWJyYnknEO64zsRvmgBMG3-DqvFgY/edit?usp=sharing)(
   ES) and leave feedback.

[#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/),
[#summary](https://make.wordpress.org/docs/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F17%2Fdocumentation-team-meeting-notes-february-17-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/)
3:16 pm _on_ February 9, 2026     
Tags: [make.wordpress.org/updates ( 55 )](https://make.wordpress.org/docs/tag/make-wordpress-org-updates/),
[p2-xpost ( 139 )](https://make.wordpress.org/docs/tag/p2-xpost/)   

# 󠀁[X-post: Documentation Team Update – February 9, 2026](https://make.wordpress.org/docs/2026/02/09/xpost-documentation-team-update-february-9-2026/)󠁿

X-comment from [+make.wordpress.org/updates](https://make.wordpress.org/updates/):
Comment on [Documentation Team Update – February 9, 2026](https://make.wordpress.org/updates/2026/02/09/documentation-team-update-february-9-2026/#comment-7053)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F09%2Fxpost-documentation-team-update-february-9-2026%2F%23respond&locale=en_US)

 [  ](https://profiles.wordpress.org/milana_cap/) [Milana Cap](https://profiles.wordpress.org/milana_cap/)
3:05 pm _on_ February 9, 2026      

# 󠀁[Documentation team meeting notes – February 3, 2026](https://make.wordpress.org/docs/2026/02/09/documentation-team-meeting-notes-february-3-2026/)󠁿

## **Housekeeping**

 * Where: [#docs](https://wordpress.slack.com/archives/C02RP4WU5)  channel on [Slack](https://make.wordpress.org/chat/)
 * When: [Tuesday, February 3 2026, 2PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260203T1400)
 * Meeting Facilitator: [@milana_cap](https://profiles.wordpress.org/milana_cap/)
 * Note Taker: [@milana_cap](https://profiles.wordpress.org/milana_cap/)
 * Agenda: [https://make.wordpress.org/docs/2026/02/03/agenda-for-discussion-meeting-september-16-2025-2/](https://make.wordpress.org/docs/2026/02/03/agenda-for-discussion-meeting-september-16-2025-2/)

_Find the complete [Transcript](https://wordpress.slack.com/archives/C02RP4WU5/p1770127227424229)
of the meeting on _[_Slack_](https://make.wordpress.org/chat/)_._

Next meeting:

 1. Where: [#docs](https://wordpress.slack.com/messages/docs/) channel on [Slack](http://www.slack.com/)
 2. When: [Tuesday, February 10 2026, 2PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260210T1400)

## Project updates

The team is exploring the idea of contributors submitting their contributions via
a form in the Docs team’s blog sidebarSidebar A sidebar in WordPress is referred
to a widget-ready area used by WordPress themes to display information that is not
a part of the main content. It is not always a vertical column on the side. It can
be a horizontal rectangle below or above the content area, footer, header, or any
where in the theme.. However, as with any form, we are facing a lot of spam submissions.
The workflow in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
is another option, but only few in Slack can create those.

[@estelaris](https://profiles.wordpress.org/estelaris/) posted [How to help with the overhaul of documentation issue tracker in GitHub](https://make.wordpress.org/docs/2026/02/02/how-to-help-with-the-overhaul-of-documentation-issue-tracker-in-github/).
She is still working on the audit, but we might as well begin updating documentation.

[@milana_cap](https://profiles.wordpress.org/milana_cap/) is actively working on
[a proposal](https://make.wordpress.org/docs/?p=68857&preview=true) for gamifying
contributions.

## Proposal for Gamifying Docs contributions

The team rewieved proposal draft and left valuable feedback. [@supernovia](https://profiles.wordpress.org/supernovia/)
noted that new contributors might feel intimidated by the low likelihood of “win”.

As the purpose of gamification is to encourage new contributors to start contributing,
as well as trying out different ways of contributing to the Docs team, in order 
to find what suits them the best, the proposal is going to be modified as follows:

 * The most points will be added for “getting started” tasks,
 * Special bonus points will be added for doing the type of task for the first time,
 * Achievements will be reflected in 2 ways: total points and/or title pathway,
 * Once the contributor earns a team membership, competition stops for them, and
   they are considered to have reached the game finish line.

[@estelaris](https://profiles.wordpress.org/estelaris/) offers her mentorship to
anyone interested in becoming a team member ❤️

[#docs](https://make.wordpress.org/docs/tag/docs/), [#meeting](https://make.wordpress.org/docs/tag/meeting/),
[#summary](https://make.wordpress.org/docs/tag/summary/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2026%2F02%2F09%2Fdocumentation-team-meeting-notes-february-3-2026%2F%23respond&locale=en_US)

## Post navigation

[← Older posts](https://make.wordpress.org/docs/page/5/?output_format=md)

[Newer posts →](https://make.wordpress.org/docs/page/3/?output_format=md)