DocsWP — WordPress Help

Documentation team meeting notes – May 26, 2026

Where: #docs channel on Slack
When: Tuesday, May 26, 2026, 14:00 UTC
Meeting Facilitator: @estelaris
Note Taker: @awetz583
Find the complete meeting on Slack.

Next Meetings

Note: There will not be a meeting on Tuesday, June 2, 2026, 14:00 UTC due to WordCamp Europe (WCEU) travel.

Planning Meeting

Where: #docs channel on Slack + Video call
When: Tuesday, June 9, 2026, 14:00 UTC

Discussion Meeting

Where: #docs channel on Slack
When: Tuesday, June 16, 2026, 14:00 UTC

View upcoming dates on the Documentation Team meeting calendar.

Updates

7.0 Release updates

  • Documentation Progress: Content updates for WordPress 7.0 are underway. @kjoyner and @awetz583, have been added as noteworthy contributors for this release and will continue drafting content for review.
  • What’s New Post: @estelaris is working on a public post highlighting the key changes in the 7.0 release.

WordCamp Europe (WCEU)

  • Event Details: WCEU Contributor Day is taking place on June 4, 2026. @estelaris and @milana_cap will be on-site to mentor and guide contributors.
  • Available Tasks: There are plenty of specific open issues ready for contributors.
  • Good First Issue: A great entry-level task for new contributors will be auditing the WordPress dashboard to map out where documentation links currently exist and brainstorm ways to improve navigation.

Documentation structure improvement proposals

@estelaris discussed a broader initiative to improve overall documentation structure. Key discussion points included:

  • Editor Integration: Exploring the ability to link directly from the WordPress editor UI to specific block documentation.
  • Dashboard Links: Providing clear internal links to DevHub, HelpHub, and Learn WordPress sites from within the WordPress admin dashboard.
  • FAQ Revamp: Redesigning and updating the current FAQ section.
  • Support vs. Documentation: The team addressed a common user confusion where documentation forms are mistaken for human support channels. Discussion focused on updating the copy to clearly distinguish static documentation from human help resources (like the support forums).

Profile Badges & Contributor Pathways

  • Contribution Badges: @estelaris has awarded profile badges to contributors from recent contributor days and WordCamp Asia. The team noted the new profile page layout, which now displays the specific dates badges were awarded.
  • Pathways Updates:  @supernovia reported that @marutim is currently testing the File a Documentation Issue pathway and providing feedback.
    • @clk87 is actively working on pathways and other documentation issues asynchronously due to timezone differences.

Handbook Translation Updates

  • Spanish Translation Review: @estelaris is updating the handbook based on recent work by a WP Credits student. After translating the material to Spanish and back-translating to English, the team identified several areas for phrasing and clarity improvements.

Standardizing Block Pages

The team is focusing on a systematic, content-first approach to update block documentation and reduce redundancy.

  • Consolidation: @kjoyner identified repetitive settings across various block documents. @estelaris confirmed the team is creating standardized “Advanced Settings” pages to consolidate these.
  • Toolbar Settings: @kjoyner will conduct a comprehensive review of repeated settings and open a proposal issue to consolidate common block toolbar documentation.
  • How to Propose Changes:
    • Create one issue focusing exclusively on one setting.
    • Include a checklist of all the block articles that need to be updated.

Tracking Gutenberg Releases

  • Core Focus Only: @estelaris proposed that when tracking Gutenberg releases for upcoming block article updates, the team should focus strictly on existing core blocks and avoid documenting experimental features.
  • Version Mapping: To check which Gutenberg versions map to specific WP Core releases, contributors should reference the Block Editor Handbook Contributor Guide.
  • Testing Tip: @milana_cap suggested using WordPress Playground as a fast, frictionless way to verify current block features and ensure documentation accuracy.

Training presentation: WP Latin America

@estelaris is designing a documentation training meetup tailored for Latin American communities.

  • Format: Presentation slides are being created in both English and Spanish, with the ultimate goal of publishing the recording to WP.tv.
  • Content Coverage:
    • Types of documentation in WP.org
    • The role and scope of the documentation team
    • Overview of HelpHub/DevHub
    • Docs issue workflow – from creation to solution

Schedule & Miscellaneous Updates

#docs, #meeting, #summary