I am using a fork of Hyde (it’s an unmaintained SSG written in Python). The markdown is generated by Python-Markdown and I am post-processing the generated HTML to change the markup used for footnotes to be able to turn them into sidenotes. Likely, I could also have written/overloaded a specific extension for Python-Markdown.
One day, I’ll rewrite all this from scratch to not depend on a specific blog engine, but for now, I live with this hacky setup. Depending on what I need, I either patch Hyde, extend it with a plugin, add a plugin for Pygments, shell-out to Node.JS (notably for CSS stuff, with PostCSS to downgrade CSS files), or add a post-build step (image minification, cache busting). It’s still quite flexible and fast enough (about 30s), even if it’s not pretty.
I am using a fork of Hyde (it’s an unmaintained SSG written in Python). The markdown is generated by Python-Markdown and I am post-processing the generated HTML to change the markup used for footnotes to be able to turn them into sidenotes. Likely, I could also have written/overloaded a specific extension for Python-Markdown.
One day, I’ll rewrite all this from scratch to not depend on a specific blog engine, but for now, I live with this hacky setup. Depending on what I need, I either patch Hyde, extend it with a plugin, add a plugin for Pygments, shell-out to Node.JS (notably for CSS stuff, with PostCSS to downgrade CSS files), or add a post-build step (image minification, cache busting). It’s still quite flexible and fast enough (about 30s), even if it’s not pretty.
score 1 · canonical