# New Playground UI > [!question] Lingering Questions > - Was the eight-button dock grouping derived from usage data about which areas users actually reach, or from the tool's internal architecture? > - Does "supports all versions of WordPress, including 0.7" mean older versions actually boot and function, or only that they're listed as selectable? > - What is the keyboard path to every dock function, and can the draggable dock be repositioned without a pointer? Unaddressed on camera. > [!tip] Article Ideas > - "Discoverability is a feature" as a standalone piece — Playground's redesign is a clean case study in a release that adds zero capability but changes what a tool effectively does. > - Time the two-click PR preview path against the old instructions and publish the actual click-count delta; the video's central claim is unmeasured and cheap to test. > [!link] Cross Reference > - [[3. Resources/MOCs/DevRel MOC]] — discoverability-as-capability and the two-click PR-preview path as a contribution-barrier reduction > - [[3. Resources/Permanent Notes/Developer-Tool Adoption Tracks Cognitive-Load Reduction Not Feature Count]] — this source is fresh evidence for an existing claim, not a new one > - [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]] — same relationship > [!quote] Vocabulary > - **Dock** — the new floating, repositionable control bar at the bottom of the Playground UI, holding eight buttons for the tool's main areas > - **Blueprint** — a Playground configuration file that boots a WordPress instance to a defined state; authored from scratch, loaded from a URL, or picked from a gallery ## Bibliographic capsule Fellyph Cintra walks through WordPress Playground's redesigned interface — a floating dock replacing the previous full-width bar — demonstrating that almost every feature it exposes (blueprint galleries, PR previews, GitHub/zip import, auto-save, file editor, database viewer, logs, three export paths) already existed; what changed is that they're now gathered into one discoverable, repositionable surface. ## Author's thesis Playground's problem was never missing capability but scattered capability, and for a tool whose entire value is speed from intent to a running WordPress instance, every click in that gap is the product — so a pure information-architecture release, honestly framed as regrouping rather than new power, is a legitimate and undervalued kind of contribution. ## Key arguments (≤3) 1. **The release is honestly framed as regrouping, not invention.** Cintra states directly that "all those options existed before, but now we group in a easy way" — the more flattering framing (presenting reorganized features as new) is available and he declines it. 2. **Two things are genuinely new, and one came from users.** The dock is repositionable with three escape modes (hide tools, drag, corner-collapse), and saved instances now render a visual preview — explicitly credited to community feedback. 3. **The redesign's central claim is asserted, not measured.** No click counts, task timings, or discoverability testing are given for old versus new — the video establishes where things now live, not that the new arrangement is actually better. ## Claim atoms ### Regrouping existing features is presented as the release itself > [!quote] ID:rw_playgroundui_h1 > All those options existed before, but now we group in a easy way. Where/why: "New" button segment. The author declines the flattering framing and names the release as information architecture rather than capability — the source's strongest and most honest claim, with reach beyond Playground. ### Community feedback produced the preview affordance Where/why: saved-instances segment. Cintra credits community feedback for instance previews — the one genuinely new user-facing affordance in the release, and a checkable, specific instance of feedback shipping rather than a vague gesture at "listening to users." ### Playground now offers every WordPress version, back to 0.7 Where/why: settings segment. Converts Playground from a testing tool into a potential historical instrument — with the caveat that "listed" is not the same as "functional," and the video demonstrates only availability, not that pre-1.0 versions actually boot. ### Page reload is distinct from instance reload Where/why: refresh-button segment. A small precision that prevents a common and costly misunderstanding during extended Playground sessions — refresh reloads the page, not the WordPress instance. ### Three separate escapes from the dock imply a known footprint cost Where/why: space-reclaiming segment (hide tools, drag to reposition, corner-collapse, full-width sticky mode). The feature set reveals a tradeoff — a persistent control surface occupies the viewport it's meant to demonstrate — that the narration never states directly. ## Permanent candidates - This source's atoms were checked against existing Permanents and found already covered — connect, don't create: - Discoverability-as-capability → [[3. Resources/Permanent Notes/Developer-Tool Adoption Tracks Cognitive-Load Reduction Not Feature Count]] and [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]] - Under-credited regrouping work → [[3. Resources/Permanent Notes/Zet · Reduce steps to first value]] and [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] - Two-click PR previews lowering review-participation cost → [[3. Resources/Permanent Notes/AI's Highest-Leverage Role in Open Source Is Communicating Intent Not Generating Code]] - No new Permanent note warranted from this source; it supplies fresh evidence for existing claims rather than a new one. ## Processing checklist - [x] Confirmed this doc's `notes` field already contained a full deep-read (Refactor Appendix present) — ported directly - [x] Checked existing Permanent notes for all candidate atoms — all already covered; connected rather than duplicated - [x] Connect into the relevant MOC — [[3. Resources/MOCs/DevRel MOC]] ## Links - [[3. Resources/MOCs/DevRel MOC]] — discoverability, contribution-barrier reduction (two-click PR previews), and community-feedback-driven shipping are direct DevRel content - [[3. Resources/Readwise/Articles/New Playground UI]] — source document