Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
rss-proxy
RSS-proxy allows you to do create an RSS or ATOM feed of almost any website, just by analyzing just the static HTML structure.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I just use the small reference C implementation of CommonMark and it works great:
https://github.com/commonmark/cmark
There is an example where you load it via shared library in Python, i.e. send a Markdown string and get back an HTML string.
I use something very similar on my website, except with a few twists - CSS, MultiMarkdown (instead of Markdown) for HTML, Perl for piping MultiMarkdown produced HTMLs through some "sed" changes, and redo instead of Make for rebuilds.
If you are looking for Make replacement - I strongly suggest taking a look at redo: https://github.com/apenwarr/redo
Have you tried https://github.com/damoeb/rss-proxy ?
Thanks! I am using MDX for the articles. I don't really like it though. MDX is fiddly and causes some headaches here and there. I am exploring other options.
The MDX files are here: https://github.com/city41/mattgreer.dev/tree/main/pages/arti...
And I just now wrote a new post about how I did the static HTML: https://mattgreer.dev/articles/how-i-built-this-static-site-...
I've found a nice middleground to be writing a custom static site generator for each site. They can be quite small (here's one[0] in ~50 lines). Usually it just loops through a directory and turns Markdown files into HTML (with header injected), and syntax highlighting.
Also, if you're really committed, you might be surprised how app-like you can make HTML+CSS, using things like checkbox and :target hacks[1]. The UI demoed in the video on this site[2] has no JS. These techniques pretty much require a generator, and there are obviously tradeoffs.
[0]: https://github.com/boringproxy/boringproxy.io/blob/master/ss...
[1]: https://www.mattzeunert.com/2017/10/30/javascript-free-todo-...
[2]: https://boringproxy.io/
Never again I will touch XSLT. That's how I dumped my wordpress to HTML. I regretted it. https://github.com/steren/wordpress-to-html
I agree wholeheartedly with this sentiment and have elected for the same thing on my website. The only difference is that I wrote a simple template based static site generator (https://github.com/JosephNaberhaus/naberhausj.com/tree/maste...) to keep my HTML sources in accordance with DRY.
What I don't understand is how the linked page is downloading 1 MB of resources which unpack to nearly 2 MB. This page shouldn't need more than 100 KB.
I made the files public temporarily: https://github.com/karoliskoncevicius/website
My website is probably a lot simpler than yours. All the "do" files are at the root level. But I have to state that there is no "redo" syntax really. You just take the scripts that do things and save them to files with a "do" extension.