---
title: "What should happen before a feature hits every plugin page? Dev Branch 32 on Playground previews"
date: 2023-10-06
author: "Courtney Robertson"
featured_image: "https://courtneyr.dev/wp-content/uploads/2026/11/dev-branch-32-playground-plugin-previews-featured.jpg"
categories:
  - name: "WordPress"
    url: "/category/wptips.md"
  - name: "Speaking"
    url: "/category/speaking.md"
---

# What should happen before a feature hits every plugin page? Dev Branch 32 on Playground previews

What should happen before a feature reaches every plugin page on WordPress.org? In October 2023, Playground previews appeared on plugin pages, then became opt out, then disappeared within hours. WPwatercooler’s Dev Branch episode 32 dug into why, and I was on the panel as a show regular.

## 🎙️ Episode details

- **Show:** Dev Branch, episode 32, “WP Playground’s Plugin Problem,” from WPwatercooler
- **Panel:** [Jason Tucker](https://profiles.wordpress.org/jasontucker/)colleague, [Jason Cosper](https://profiles.wordpress.org/boogah/)acquaintance, [Sé Reed](https://profiles.wordpress.org/sereedmedia/)colleague, [Matt Cromwell](https://profiles.wordpress.org/webdevmattcrom/)colleague and me, Courtney Robertson
- **Date:** October 6, 2023
- **Topics:** what broke with Playground previews, where the conversation happened, and what launches need
- **Show notes:** [Dev Branch episode 32, with a transcript](https://www.wpwatercooler.com/devbranch/ep32-wp-playgrounds-plugin-problem/)

 Captions and an interactive transcript are in the player controls (Transcript button).The episode recording, with the publisher’s captions and an interactive transcript in the player.

## 🧩 What broke with Playground previews, and why

The idea is great in theory: click a button on a plugin page and try it in a live WordPress. In practice, plugins with dependencies didn’t work, as [Andy Fragen](https://profiles.wordpress.org/afragen/)colleague pointed out, and that’s a lot of the directory. Extensions built on WooCommerce, including the SkyVerge plugins I watched for GoDaddy, fell into that group. Drawing on points Mika Epstein raised, I said at least a third of the directory wouldn’t work with it. CoBlocks, another plugin I followed for GoDaddy, had been in the original demos.

## 📣 Where was the conversation?

I’d been facilitating Meta team meetings, and I tried to read every Meta Trac ticket. Before launch, the only discussion happened in a single Meta Trac ticket, plus the meta commits channel in Make WordPress Slack. However, there was little activity until it shipped. Also, no one called in the teams and plugin authors who would be affected.

Timing mattered too. Trust in the plugin directory was still recovering from earlier controversies, so another surprise there landed hard.

## 🛠️ Engineers engineer; launches need more

Next, I asked Matt Cromwell, who led development teams, whether his senior developers also ran product launches. My point: engineers do engineering well, but a feature launch that touches thousands of plugin authors needs communication, opt in planning and someone to tell the community what’s coming.

## 🧪 What can you take from the Playground previews launch?

- **Plugin authors:** watch Meta Trac and the meta commits channel for changes to your plugin page.
- **Project teams:** pair every directory wide feature with a communication plan and an opt in period.

Also, more conversations like this one live in [my podcast and speaking archive](https://courtneyr.dev/category/speaking/).

## 🗓️ Archival note

WPwatercooler’s episode page is dated October 6, 2023. Then I added this post on November 9, 2026, from the show notes and the publisher’s transcript. However, I reviewed the transcript, not the recording.





[](https://courtneyr.dev/2023/10/06/dev-branch-32-playground-plugin-previews/)Courtney RobertsonWhat should happen before a feature hits every plugin page? Dev Branch 32 on Playground previews