- 'noping' setting to create ping files, but don't actually send webmentions
- watermark size back to older setting
- changed sharpend in unsharp mask settings
- added is_photos setting which applies if all images are photos
- got rid of bleach and reacji detection, nobody is using it
- removed google vision and google text classification
- 410 for ^/tag and ^/comment
- 80x15 SVG bottom banners
- better code syntax hightlight CSS
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
- 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
- removed the abomination experiment (aka microdata)
- added svg source icomoon for the possibility to extend later
- rsync moved into nasg.py itself, so the ordering of render - sync - webmentions is ok
- 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.
