-
-
Notifications
You must be signed in to change notification settings - Fork 16.5k
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
collapsible markdown is not parsed properly in a page layout #1363
Comments
This isn't an issue with this theme but just with your plugin/gem configuration. This can be shown by just replacing your page layout with none. If you serve that page locally you will see that you are still seeing the issue that you are describing above. I looked at the Github Pages documentation about what plugins to use at Plugins and added those plugins to my _config.yml and Gemfile without successfully producing the expected page. Obviously, Github is doing something different when processing pages through its Github site compared to how Github Pages does it. As an aside, Github Pages publishes a list of all its dependency they use at GitHub Pages Dependency versions. In the end, it seems to me that Github just needs to clarify how they generate the markdown files through the github website compared to how github pages does it. |
Thanks for looking into this! I will just refrain from using the |
According to this comment, and after testing it myself, it seems that the culprit was that kramdown by default doesn't support markdown inside tags. But you can enable it by add a config parameter. I tested this and it indeed works. |
Thanks for investigating further. To add, adding a markdown="1" attribute to the |
I have a page layout with markdown. Since the content is long, I enclosed each section in a collapsible section using the
<details>
tag following this article. The markdown itself is rendered properly in github (see my page for example) but somehow the markdown format is not rendered properly after publishing (see rendered my page), perhaps due to conflict with css?The text was updated successfully, but these errors were encountered: