DevHub link to Documentation, Playground landing page move

[courtneyr-dev]

Proposing an update to accessing developer docs in https://meta.trac.wordpress.org/ticket/7334.

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.

Related issues

The above work is tracked in these issues:

• Move developer.wordpress.org/playground to wordpress.org/playground wporg-main-2022#355
• Redirect developer.wordpress.org/playground to wordpress.github.io/wordpress-playground/ wporg-developer#412

[adamziel]

Good thinking @courtneyr-dev! Let me paraphrase to confirm I understand:

• https://WordPress.org/Playground would be the page containing a general description
• https://developer.wordpress.org/playground would redirect to the documentation page

I think that makes a lot of sense. @StevenDufresne what would it take to move the existing https://developer.wordpress.org/playground site to the top-level domain and put a redirect to https://wordpress.github.io/wordpress-playground/ in its place?

[courtneyr-dev]

Yes @adamziel that's the idea to match the flow of the rest of DevHub going to docs.

[StevenDufresne]

Makes sense to me.

When you are ready, can you split this up into 2 tickets?

• https://github.com/wordpress/wporg-main-2022 for the top-level page
• https://github.com/wordpress/wporg-developer for the redirect (I think this is where it belongs. I can move it if not)

[adamziel]

Just opened two issues:

• Move developer.wordpress.org/playground to wordpress.org/playground wporg-main-2022#355
• Redirect developer.wordpress.org/playground to wordpress.github.io/wordpress-playground/ wporg-developer#412

[StevenDufresne]

Those two issues are not closed. Please verify.

[adamziel]

Looks great to me, thank you so much @StevenDufresne!