In contrast to what I wrote 1,5 years ago it’s now possible to use all of GitHub Flavored Markdown’s features combined with footnotes and syntax highlighting on your Jekyll site whilst still having GitHub Pages build your site for you. Building your site locally and then pushing the resulting HTML is a thing of the past! :)
After I decided to switch this blog over from Jekyll to Nikola the first thing to do was to configure Nikola to my liking. Nikola offers plenty of options to configure, as of this writing it has more than 100 settings for all of its options! Since I want something as lean as possible some tweaking and workarounds were necessary to make it work the way I wanted to. This post will cover the way I configured Nikola.
Just quick heads-up in case someone is wondering why his or hers
<h1> isn’t looking like they expect.
Modern browsers apply different styling for
<h1> elements inside a
<div> vs inside one of the new semantic elements like
This is because these new semantic elements influence the document outline and the modern browsers try to show that to you in a graphical way.
See this new post for more details.
Jekyll uses redcarpet as it’s default Markdown parser for newly generated sites as of version v1.1.0. It does so by setting
markdown: redcarpet in
Redcarpet is the markdown parser used by GitHub, but in it’s default config it actually doesn’t parse using the GitHub Flavored Markdown (GFM) rules.