I recently forked the repository to build my own personal website. Everything was going smoothly until I tried to add 2 new pages. The first page was a markdown file, and the second was an html file that used Liquid tags. However, when launching the site with jekyll's server (bundle exec jekyll serve), I noticed that all of the markdown and liquid templates were rendering on the page without being processed, as if the content matched the source files.
This overwrites Jekyll's intended purpose of the global content variable, which is to represent the rendered version of a page's content.
... the rendered content of the Post or Page being wrapped. Not defined in Post or Page files.
So I am curious if there is any reason for overriding this variable? It may cause others the same headache. I have removed the assignment from my fork and have not yet seen any side effects. I am happy to open a PR if it is indeed unneeded.
The text was updated successfully, but these errors were encountered:
I recently forked the repository to build my own personal website. Everything was going smoothly until I tried to add 2 new pages. The first page was a markdown file, and the second was an html file that used Liquid tags. However, when launching the site with jekyll's server (
bundle exec jekyll serve), I noticed that all of the markdown and liquid templates were rendering on the page without being processed, as if the content matched the source files.After digging for a while, I realized that the file
_includes/header.htmlassigns thecontentvariable topage.content.This overwrites Jekyll's intended purpose of the global
contentvariable, which is to represent the rendered version of a page's content.So I am curious if there is any reason for overriding this variable? It may cause others the same headache. I have removed the assignment from my fork and have not yet seen any side effects. I am happy to open a PR if it is indeed unneeded.
The text was updated successfully, but these errors were encountered: