Proposal: Workshop Submission and Review Process for Learn WordPress

Since we’ve been talking about moving beyond events when it comes to online WordPress content, and there’s an application form available for anyone who would like to assist with reviewing submitted workshops, this is a good time to discuss the submission and review process for workshops submitted to the Learn WordPress platform, which is intended to be hosted on

This process needs to be simple enough that it doesn’t discourage people from submitting their content, and open enough so that reviewers can collaborate on the process effectively. Here’s a proposal for how this could work:

Step 1: A presenter submits their workshop details in a custom form, which saves their details as a new post in the same post type that published workshops are stored in, but in draft status. This will sound familiar to 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. organisers as it’s exactly how WordCamp session submissions work.

Step 2: Reviewers are given a user role that permits them to edit posts in the workshop post type (possibly editor or a custom user role if necessary). They can log in to review the workshop and leave notes on it as needed. These notes can be viewed by other reviewers to facilitate collaboration in the process.

Step 3: For a workshop that is approved, the reviewer would then request any additional info from the presenter (likely using the Help Scout instance for communication), and inform them that they should go ahead and record the workshop. This means that presenters don’t unnecessarily spend the time recording content that is not going to be used.

Step 4: The recorded workshop (hosted on, along with any other missing info, is added to the post and it is scheduled to be published if it passes a final review of the content itself.

This process enables collaboration between reviewers and minimises any friction in the process.


  1. Does this process sound open and collaborative enough for this kind of platform?
  2. Is there anything that you would change in the steps outlined above?

I have also added this as an issue on the Learn WordPress GitHub repository, so any relevant discussion and points from this post will be copied over there to update that proposal.