- checking text against google natural language api: the strict classification it offers is better, than free folksonomy, if I ever want to connect entries based on topic
unfortunately they don't support Hungarian yet.
- fixing google disagreements on what is needed in a hatom/hentry
- adding a bit of invisible contact information in json-ld to see if anything picks it up
- fixing border issue in menu css
- fixed gone_re php regexes
- better nav header layout
- follow page instead of direct RSS link
- logger in settings for nasg instead of direct logging
- prism.js only for articles with language code blocks
- added webmention.io webhook to email template
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.
While Pandoc was generating something sane, the output of CodeHilite puts silly amount of extra text and makes the HTML output completely unreadable.
In the end, it still looks like prism.js is a nice and solid solution, even if it's JS.
I'll explore other options, but so far, it's either back to Pandoc, or sticking with Prism.
