becase it's easy to write, forces me to use some sort of structure, and it might come handy.
However, the end HTML is microformats v1 and v2 - v1 for google, search engines, etc, v2 for anything indieweb.
- added og: and article: from open graph to meta
- jsonld as tmplvars for most elements
- removed unused commented code
- indention for inline CSS for readability
- merged reactions and comments into a single block
- relurl filter is ready, but not yet in use, because it's a mess
- reworked yearly archives: all page shows all years, no prev/next
- removed property= mf2 tags
- cleanups in markup
- added searchaction schema.org thing
- removed everything-the-same-size-font from style
So, Python Markdown is a bottomless pit of horrors, including crippling parsing bugs,
random out of nowhere, lack of features. It's definitely much faster, than
Pandoc, but Pandoc doesn't go full retard where there's a regex in a fenced code block,
that happens to be a regex for markdown elements.
Also added some ugly post string replacements to make Pandoc fenced code output work
with Prism:
instead of the Pandoc <pre class="codelang"><code>, Prism wants
<pre><code class="language-codelang>, so I added a regex sub, because it's 00:32.
