Skip to content

Corrected numbering issue on- How to Install and Configure Playground…#159

Open
iamsohilvahora wants to merge 4 commits intoWordPress:trunkfrom
iamsohilvahora:fix/get-setup-for-testing-page-numbering
Open

Corrected numbering issue on- How to Install and Configure Playground…#159
iamsohilvahora wants to merge 4 commits intoWordPress:trunkfrom
iamsohilvahora:fix/get-setup-for-testing-page-numbering

Conversation

@iamsohilvahora
Copy link
Copy Markdown
Contributor

image

@github-actions
Copy link
Copy Markdown

github-actions Bot 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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: iamsohilvahora <sohilvahora96@git.wordpress.org>
Co-authored-by: ozgursar <ozgursar@git.wordpress.org>
Co-authored-by: 3kori <r1k0@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@ozgursar
Copy link
Copy Markdown
Collaborator

I think there should no numbering after the 4. Finally, run the long npx command below: and the code snippet below that.

So, instead of fixing numbering of list items, I think we need to remove them from list and make normal paragraphs. What do you think?

nobullet

@3kori
Copy link
Copy Markdown
Collaborator

3kori commented Apr 29, 2026

So, instead of fixing numbering of list items, I think we need to remove them from list and make normal paragraphs. What do you think?

I agree

@iamsohilvahora
Copy link
Copy Markdown
Contributor Author

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.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here


5. Your WordPress instance should now be accessible at: [http://localhost:9400](http://localhost:9400)

<p>
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need p tags for markdown?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, Should remove it? and keep only text?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

md-preview

@iamsohilvahora iamsohilvahora requested a review from ozgursar May 1, 2026 13:19
@@ -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>
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member

@huzaifaalmesbah huzaifaalmesbah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ozgursar, Hello @iamsohilvahora I have suggest remove p tag and also add backticks.

Comment on lines +99 to +105
<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>
Copy link
Copy Markdown
Member

@huzaifaalmesbah huzaifaalmesbah May 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The a tags are also not necessary; we can use MD links

http://localhost:9400

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<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.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
</p>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants