Move developer.wordpress.org/playground to wordpress.org/playground #355
Comments
|
Thinking more about this, how many links are in the wild suggesting How are we going to cater to those users? Add something in the docs?
|
bazza
pushed a commit
to WordPress/wordpress.org
that referenced
this issue
Dec 12, 2023
…ion. This is a 302 as the playground will be available at this url directly in the future. See https://wordpress.slack.com/archives/C02QB8GMM/p1702348887775449 See WordPress/wporg-main-2022#355 git-svn-id: https://meta.svn.wordpress.org/sites/trunk@13050 74240141-8908-4e6f-9713-ba540dce6ec7
|
@StevenDufresne Yes, updating the docs seems like the best way forward. I'll add a note at the top along the lines of:
|
|
How about this? WordPress/wordpress-playground#866 |
adamziel
added a commit
to WordPress/wordpress-playground
that referenced
this issue
Dec 14, 2023
## What is this PR doing? The ticket at WordPress/wporg-main-2022#355 looks into: * Moving the Playground website from https://developer.wordpress.org/playground/ to wp.org/playground * Redirecting from https://developer.wordpress.org/playground/ to the documentation However, there are already some websites out there linking to https://developer.wordpress.org/playground/. This PR adds a visible link at the top of the main docs page for anyone who might get to the docs site there and be confused: <img width="1207" alt="CleanShot 2023-12-12 at 23 11 22@2x" src="https://github.com/WordPress/wordpress-playground/assets/205419/4a4bb337-8a2c-404b-b148-6589138abe5f">
|
Done. |
renintw
pushed a commit
to renintw/wordpress.org
that referenced
this issue
Jan 28, 2024
…ion. This is a 302 as the playground will be available at this url directly in the future. See https://wordpress.slack.com/archives/C02QB8GMM/p1702348887775449 See WordPress/wporg-main-2022#355 git-svn-id: https://meta.svn.wordpress.org/sites/trunk@13050 74240141-8908-4e6f-9713-ba540dce6ec7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in WordPress/wordpress-playground#728, a Playground overview page makes a lot more sense under the top-level wordpress.org site. To quote @courtneyr-dev:
Let's make sure it's available on https://wordpress.org/Playground. Technically that could mean either moving developer.wordpress.org/playground there, or creating a new site and populating it with the same content.
Once that's in place, the next step would be to ship the documentation on the developer.wp.org site. I created a separate issue to track it here: WordPress/wporg-developer#412
@StevenDufresne suggested opening a ticket here to make that happen.
The text was updated successfully, but these errors were encountered: