-
Notifications
You must be signed in to change notification settings - Fork 59.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add note on gh-pages for formatting within <details>
block
#34567
Conversation
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
@nisbet-hubbard Thanks so much for opening a PR! I'll get this triaged for review ✨ |
Hi @nisbet-hubbard, could I ask which renderer you were trying to use (that prompted this suggestion)? Was it Jekyll? Many thanks. |
Yes, it was Jekyll! |
Thank you—I think this covers the same issue: #32988 Because of 32988, we've got an issue in our backlog that we'd like to complete internally. The solution we agreed on (that is, adding product callouts) will affect quite a few different pages when we implement it. I'll copy @nguyenalex836 in case I've missed something, but I'm afraid we'll need to close this in favour of our internal issue (I'll raise its priority). Thank you for your interest in the Docs and helping other users 🙏 |
Why:
Markdown formatting doesn’t render properly for gh-pages.
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).
data
directory.For content changes, I have completed the self-review checklist.