Topic
Define a clear, sustainable workflow for turning meeting notes into published blog posts – including who takes notes, how corrections work, and how the GitHub draft becomes a Make WordPress blog post.
Why this topic?
Several community members expressed interest in contributing to documentation:
- @sibokul: "For note taking, volunteers can be asked to participate. Particularly I'm interested to do this."
- Sumit Singh (Team Rep, via Slack): Offered to publish monthly recap posts.
The current workflow (GitHub draft → 48h review → Make WordPress blog post) is documented in this repo, but the team should discuss and confirm it in practice.
Suggested discussion questions
- Who takes notes during the meeting, and how are they structured?
- How does the ~48h GitHub review work in practice – who is notified?
- Who has editor access to publish on make.wordpress.org/training?
- Could we build a pool of rotating note-takers (similar to moderators)?
- What's the minimum viable note for publication?
Proposed by
@sibokul and Sumit Singh (via blog comment and Slack, March 2026)
Topic
Define a clear, sustainable workflow for turning meeting notes into published blog posts – including who takes notes, how corrections work, and how the GitHub draft becomes a Make WordPress blog post.
Why this topic?
Several community members expressed interest in contributing to documentation:
The current workflow (GitHub draft → 48h review → Make WordPress blog post) is documented in this repo, but the team should discuss and confirm it in practice.
Suggested discussion questions
Proposed by
@sibokul and Sumit Singh (via blog comment and Slack, March 2026)