-
-
Notifications
You must be signed in to change notification settings - Fork 16.2k
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
Post preview shows markdown #1322
Comments
This is unfortunately working "as intended". It's not really an issue specific to this theme, it's a more general jekyll concern. I'm going to close this issue since it's not a bug with my theme, but I'll try to walk you through what's happening, so that you can try to think of a custom solution or take this info and ask in a jekyll forum about work arounds: Jekyll has the concept of a "post excerpt" as described here https://jekyllrb.com/docs/posts/#post-excerpts and as you can see, by default it takes the first paragraph of content. Here if the code in beautiful jekyll that takes this excerpt and shows it on the home page: beautiful-jekyll/_layouts/home.html Lines 75 to 76 in b57d3d4
So what's happening is that because you have a blank line inside that (poem?), jekyll treats that as a new paragraph. So it takes all the content up until that blank line, which is:
And this it the post excerpt (if you use the To drive this point further, I think (I haven't tested this) that if you remove blank lines from the poem, or if you ended the markdown syntax after the first paragraph, then the post excerpt on the home page will look correct. You can also explicitly define what the excerpt should be, by adding a I hope this was useful. |
Oh wow that's a very thorough response! That all makes perfect sense, I'll play around with some settings, thanks! |
👋 I'm trying out Beautiful Jekyll for a site and noticed that my post, which starts with a markdown code block is rendered quite literally in the home pages summary (E.g. the summary starts with "```text")
(Also love it so far, thanks for making this ❤️)
The text was updated successfully, but these errors were encountered: