Corrected numbering issue on- How to Install and Configure Playground…#159
Corrected numbering issue on- How to Install and Configure Playground…#159iamsohilvahora wants to merge 4 commits intoWordPress:trunkfrom
Conversation
iamsohilvahora
commented
Apr 25, 2026
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
I agree |
|
I agree, let me update. |
| <p>You may also consider creating an alias for this long command in your terminal, so that you don't need to remember and type it every time.</p> | ||
|
|
||
| 7. Optionally, you can mount your `themes` folder if you will be adding code snippets into your active theme's `functions.php` file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. | ||
| <p>Optionally, you can mount your <code>themes</code> folder if you will be adding code snippets into your active theme's <code>functions.php</code> file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. |
There was a problem hiding this comment.
Why did you change the markdown backticks to code tags?
| <p>Optionally, you can mount your <code>themes</code> folder if you will be adding code snippets into your active theme's <code>functions.php</code> file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. | ||
|
|
||
| Here is how you would mount the `themes` folder alongside the `plugins`. | ||
| Here is how you would mount the <code>themes</code> folder alongside the plugins. |
|
|
||
| 5. Your WordPress instance should now be accessible at: [http://localhost:9400](http://localhost:9400) | ||
|
|
||
| <p> |
There was a problem hiding this comment.
Do we need p tags for markdown?
There was a problem hiding this comment.
No, Should remove it? and keep only text?
There was a problem hiding this comment.
We don't need p tags here as well as the code tags. We must use Markdown as much as possible. They will get converted to HTML when PR is merged.
Please check the existing handbook pages, you will see that we never used p or code tags. Instead we use backticks for inline code and triple backticks for codeblock.
I use this VSCode Extension for editing and previewing Markdown files:
https://marketplace.visualstudio.com/items?itemName=shd101wyy.markdown-preview-enhanced
| @@ -104,9 +104,9 @@ Your WordPress instance should now be accessible at: <a href="http://localhost:9 | |||
|
|
|||
| <p>You may also consider creating an alias for this long command in your terminal, so that you don't need to remember and type it every time.</p> | |||
There was a problem hiding this comment.
Sorry but you have removed the inline code that were between backticks.
Also p tags are still in the code.
Maybe you can consider starting with a brand new branch from the trunk and only fix the bullet points without changing the remaining markup.
huzaifaalmesbah
left a comment
There was a problem hiding this comment.
Thanks @ozgursar, Hello @iamsohilvahora I have suggest remove p tag and also add backticks.
| <p> | ||
| Your WordPress instance should now be accessible at: <a href="http://localhost:9400">http://localhost:9400</a> | ||
| <br /> | ||
| <img src="https://make.wordpress.org/test/files/2026/04/playground-cli-in-browser-scaled.webp" alt="WordPress Playground running locally on port 9400" style="max-width: 100%"> | ||
| </p> | ||
|
|
||
| <p>You may also consider creating an alias for this long command in your terminal, so that you don't need to remember and type it every time.</p> |
There was a problem hiding this comment.
| <p> | |
| Your WordPress instance should now be accessible at: <a href="http://localhost:9400">http://localhost:9400</a> | |
| <br /> | |
| <img src="https://make.wordpress.org/test/files/2026/04/playground-cli-in-browser-scaled.webp" alt="WordPress Playground running locally on port 9400" style="max-width: 100%"> | |
| </p> | |
| <p>You may also consider creating an alias for this long command in your terminal, so that you don't need to remember and type it every time.</p> | |
| Your WordPress instance should now be accessible at: `http://localhost:9400` | |
| <br /> | |
| <img src="https://make.wordpress.org/test/files/2026/04/playground-cli-in-browser-scaled.webp" alt="WordPress Playground running locally on port 9400" style="max-width: 100%"> | |
| You may also consider creating an alias for this long command in your terminal, so that you don't need to remember and type it every time. |
There was a problem hiding this comment.
The a tags are also not necessary; we can use MD links
There was a problem hiding this comment.
@3kori Thanks for pointing that out. I’ve updated it.
| <p>You may also consider creating an alias for this long command in your terminal, so that you don't need to remember and type it every time.</p> | ||
|
|
||
| 7. Optionally, you can mount your `themes` folder if you will be adding code snippets into your active theme's `functions.php` file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. | ||
| <p>Optionally, you can mount your themes folder if you will be adding code snippets into your active theme's functions.php file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. |
There was a problem hiding this comment.
| <p>Optionally, you can mount your themes folder if you will be adding code snippets into your active theme's functions.php file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. | |
| Optionally, you can mount your `themes` folder if you will be adding code snippets into your active theme's `functions.php` file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. |
| <p>Optionally, you can mount your themes folder if you will be adding code snippets into your active theme's functions.php file and want to keep the changes between rebuilds. To avoid affecting future tests, don't forget to remove any custom code snippets you have added. | ||
|
|
||
| Here is how you would mount the `themes` folder alongside the `plugins`. | ||
| Here is how you would mount the themes folder alongside the plugins. |
There was a problem hiding this comment.
| Here is how you would mount the themes folder alongside the plugins. | |
| Here is how you would mount the `themes` folder alongside the `plugins`. |
| ``` | ||
|
|
||
| 6. You may also consider creating an alias for this long command in your terminal, so that you don't need to remember and type it every time. | ||
| </p> |
