[wp-meta] [Making WordPress.org] #7334: Proposal to Update WordPress Playground URLs and Content

Making WordPress.org noreply at wordpress.org
Tue Oct 31 15:05:08 UTC 2023


#7334: Proposal to Update WordPress Playground URLs and Content
---------------------------+---------------------
 Reporter:  courane01      |       Owner:  (none)
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:
Component:  Developer Hub  |  Resolution:
 Keywords:                 |
---------------------------+---------------------

Comment (by courane01):

 A few user stories to clarify:

 == User Stories

 **As a** WordPress developer,
 **I want** straightforward access to developer resources when navigating
 to documentation URLs,
 **So that** I can efficiently find the information I need to enhance my
 projects.

 == 🌐 **Scenario:** Seeking Developer Documentation

 **Given** I am a developer looking for documentation and resources,
 **When** I navigate to `https://developer.wordpress.org/playground`,
 **Then** I expect to find developer documentation and resources directly
 relevant to my needs.

 == 🔄 **Scenario:** Encountering WordPress Playground Description

 **Given** I am directed to a landing page describing what WordPress
 Playground is,
 **When** I am searching for developer documentation,
 **Then** I feel it hinders my journey to finding the necessary resources
 quickly,
 **And ** The Playground description would be better suited at a more
 general URL.

 == 🔄 **Scenario:** Redirecting to Top Level for WordPress Playground
 Introduction

 **Given** the general introductory nature of the content currently at
 `https://developer.wordpress.org/playground`,
 **When** I think of where to find such introductory information,
 **Then** I expect it to be located at a top-level domain such as
 `https://WordPress.org/Playground`,
 **And** I would appreciate a direct link from the main navigation menu to
 discover what WordPress Playground is all about easily.

 == 🔄 **Scenario:** Accessing Developer Documentation

 **Given** the proposal to realign the URLs and content,
 **When** I now navigate to `https://developer.wordpress.org/playground`,
 **Then** I am redirected to a page with active developer resources and
 documentation,
 **And** my experience aligns with my expectations as a developer seeking
 technical information.

 == 🎉 **Scenario:** Improved Navigation and Logical Content Placement

 **Given** the proposed URL and content realignment,
 **When** I navigate through the WordPress domains,
 **Then** I find a logical, intuitive structure that guides me to the right
 resources,
 **And** I appreciate the enhanced user experience that saves me time and
 aligns with my goals as a developer,
 **So that** I am encouraged to explore, learn, and contribute more within
 the WordPress community.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7334#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list