Quick summary
Our cohort showed this: interest in the Block 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 is high, recordings help — but they don’t replace live energy. Going forward, we’ll focus more on short tasks with feedback, clear guidance upfront, regional times/languages, and inviting via Meetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area.. Less lecture, more hands‑on.
What it was about?
At the end of 2024, Lax Mariappan @lakshmananphp and Jonathan Bossenger @psykro ran a successful cohort based on the Beginner Developer Learning Pathway. We’re building on that: the focus is practical learning and confident use of the Block Editor.
Led by Muhibul Haque @devmuhib, we kicked off a “Block Editor Basics” cohort — as a complement to Learn WordPress and with a train‑the‑trainer mindset: participants should use the Block Editor confidently and be able to host their own workshops or cohorts. In six weekly online sessions (60–90 minutes), we covered layout blocks, Patterns, the Site Editor, and Templates — with demos, exercises, and Q&A. On 28 Sep 2025, a shared retrospective wrapped up the cohort.
How the cohort went?
Leads
Host: Muhibul Haque @devmuhib
Co‑host: Rico F. Lüthi @rfluethi
Participants
@bigod, @Chris Ober, @dilip2615, @gcordner, @mosescursor, @dparthj, @rahmatgumilar, @talha74, @tuba121, @vasantrajput
Topics across six sessions
Basics & layout (Group/Row/Stack/Grid), Columns & Cover, List/Gallery/Code, Managing Patterns, Site Editor & Templates/Template Parts, Tables & Shortcodes, plus best practices/theme blocks.
What worked well?
- Recordings helped those who missed sessions keep up and provide material for future lessons/workshops.
- There’s clear interest in advanced topics. An optional advanced track (e.g., REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/., block/theme development, debugging, performance) makes sense.
- Small‑group work, focused Q&A blocks, and short tasks raised engagement without taking over the whole slot.
- Learning pathways give orientation and can improve completion rates.
Where it was bumpy?
- Time slot: 13:00 UTC meant 20:00 in Indonesia and 06:00 in the US — tough on a Sunday.
- Reach: announced only in Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.; the term “cohort” is confusing for some.
- Format: sometimes too passive. Some felt live tasks slowed things down, others wanted exactly that. PDFs without direct task ties were used less.
- Interaction: no shared space (instead of DMs) — the group dynamic suffered.
- Content: unclear whether “Classic vs Block Themes” is really needed.
- Recordings sometimes reduced the motivation to join live (“I’ll watch later”).
- Recordings: how we handle them afterward was open.
From these learnings, we’re making four concrete, immediately actionable changes.
What we’re changing now?
Communication and participation
- Kick‑off via Meetup.com with prerequisites, flow, and time commitment before sign‑up. After that, the cohort is closed.
- Make time commitment transparent: 60–90 min live weekly plus 30–60 min tasks.
- Offer regional cohorts in local times and languages to better address language barriers and time zones.
- We’ll clarify recordings before the start and explain in the kick‑off how we’ll handle them.
- Consider highlight clips (5–10 min) instead of full replays to keep live sessions valuable — but note this requires significant additional moderation effort.
Teaching approach
- Shorter follow‑along tasks with feedback right after demos.
- Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tasks as homework with clear submissions and checks.
- Small‑group phases and focused Q&A for more activation.
- A project running across the series: developed as homework, presented to the group at the end.
- Level‑tasks: simple live tasks plus optional advanced homework — so both beginners and fast learners benefit.
- Spotlight moments in live sessions where participants share progress.
Content
- Gather prerequisites and needs upfront (incl. “Classic vs Block Themes”) and make them transparent in the kick‑off.
- Easy‑to‑follow examples to build — live or as homework. Optional advanced track in small groups.
Community and recognition
- A shared space just for the group between sessions is essential for momentum and learning success. A DM channel isn’t suitable.
- Try badges/certificates (e.g., ≥ 80% attendance + project completion) for more commitment.
- Add spotlight moments in live sessions where participants share progress. Recognition motivates — knowing you might be “in the spotlight” increases homework completion.
- Surface real, varied participant examples (beyond trainer demos) to broaden perspectives and reinforce learning.
Thanks and what’s next?
Thanks to all participants and contributors. We’ll continue the cohort in a more hands‑on, interactive, and language‑accessible way, with clear tasks, follow‑along moments, and better reach. Want to host a local cohort? Get in touch — we’ll help with the setup.
