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: ekamran <ekamran@git.wordpress.org>
Co-authored-by: huzaifaalmesbah <huzaifaalmesbah@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.

Thank you for the PR @ekamran. However, it doesn't address the main issue in #175. For example, this paragraph in the Database Inspection page gets treated as a code block.

Since the syntax of that paragraph and the inline code looks correct and should be parsing accordingly. I opened #175 to hear from others what might be the root cause of the problem and how we can fix it.

Make another commit if you have a fix for the problem.

Thanks for checking this.

I agree, the original Markdown syntax looks valid and GitHub renders it correctly. So this seems more like a Make Handbook rendering/sync issue than a normal Markdown issue.

I tried a possible workaround using HTML <code> tags for the affected inline code, but I am not fully sure that is the right fix because it only avoids the parser issue for this paragraph. It may not address the actual root cause.

So I think it is better to wait for input on #175 before adding another commit, unless the team prefers the workaround approach.

We try as much as possible to avoid using HTML tags within the MD files. I think the best approach would be to remove the inline code (`) characters entirely.

Thanks, I checked this a bit more.

The source Markdown looks valid and GitHub renders it correctly, but the live Make page output seems to be malformed.

For the Database Inspection page, the live HTML currently renders the paragraph like this:

Then open http://localhost:8080` in your browser. This uses the default local database credentials from the WordPress development environment. The default database name iswordpress_develop`.

The Markdown export also looks corrupted here:
https://make.wordpress.org/test/handbook/get-setup-for-testing/database-inspection/?output_format=md

So it looks like the issue is happening somewhere in the Make Handbook sync/rendering pipeline, not in GitHub Markdown itself.

For this PR, I can still make the requested workaround commit by removing the inline-code backticks from the affected Database Inspection paragraph. But I think the root cause may need a Meta ticket so other handbook pages with valid inline code do not keep hitting the same issue.

I noticed this issue only occurs with localhost URLs that include a port number when we use inline code formatting. As a simple fix, we can remove the backticks(`) and use normal text instead—there's no need for inline code formatting in this case.

Otherwise, we'll need to investigate further to understand how we can properly fix the issue. If necessary, we may need help from the Meta team. For now, though, I think the simplest approach is to remove the backticks from these pages:

• https://make.wordpress.org/test/handbook/get-setup-for-testing/email-testing/
• https://make.wordpress.org/test/handbook/get-setup-for-testing/database-inspection/
• https://make.wordpress.org/test/handbook/get-setup-for-testing/test-core-tickets-with-playground/
• https://make.wordpress.org/test/handbook/get-setup-for-testing/set-up-a-testing-environment/

Thanks for the review.

I pushed a follow-up commit and narrowed the PR scope. It now only removes inline-code formatting from the localhost URLs with port numbers on the four affected pages.

The PR diff should now be 4 files with one line changed in each file. I also reverted the extra cleanup changes so this stays focused on #175.