Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Allow markdown to not be compiled to html #1216

davegandy opened this Issue Jun 15, 2013 · 4 comments


None yet
5 participants

Apologies if my answer to this issue is somewhere and I missed it.

I'm using Jekyll to manage and build Font Awesome. I would like to include site variables in README.md and other markdown files. By default, these files are getting compiled down to html. Is there a way to pass these files through the templating engine and leave them as markdown files?


parkr commented Jun 15, 2013

Hey Dave! Congrats on your latest release - glad Jekyll can be of some assistance in your work.

As of right now, every page is rendered as follows:

  1. Render Liquid
  2. Convert if a converter exists for that extname (e.g. .markdown)
  3. Render layout(s) recursively

That produces the final HTML. In the present code, as I understand it, there is no way to get around the markdown to HTML conversion. This conversion has been baked in since the early days because our mission is to make static sites, and HTML is the language of the browser so it just made sense to spit out HTML at the end of compilation.

To get around this, I'd write a plugin (generator) that renders the liquid based on the site passed into the generate function.


envygeeks commented Jun 17, 2013

Kill off Jekyll's markdown processor by changing the markdown extension to ".jekyll" and then create your own markdown processor. This could be solved with my additions but here it's simple enough to kill off Jekyll's processor, here is an example of doing that: https://gist.github.com/envygeeks/5799659#file-html-pipeline-rb-L27


penibelst commented May 12, 2014

@jekyll/owners: can be closed.


parkr commented May 12, 2014

@envygeeks's suggestion is the only possibility at this point.

@parkr parkr closed this May 12, 2014

@jekyllbot jekyllbot locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.