51–60 of 137 posts
A tiny bit of webdev-side dynamicism can really help with managing visitor-side static websites built on .html files in directories. If you run your own webserver and write HTML then check out server side includes. Being able to include .html fragments in other .html files means no need to edit the same bit in dozens of .html files (ie, left_menu.html, footer.html, etc). And since SSI hasn't really changed in 20 year…
> However, even a static site generator will deprecate some features one day No? You don't need to upgrade to the version that deprecates. Besides, what features are you using with such a simple blog the are at risk?
I used wintersmith.io. At some point it was abandoned and eventually the node version needed was old and other stuff associated with it. It became a hassle.
I too take a basic approach, where I use pandoc to generate HTML according to a template, but I'm lacking an RSS feed. That's a bit fiddly to hack up.
https://dthompson.us/projects/haunt.html looks okay.
I'm blogging with Raw HTML since the beginning of this year. The biggest missing piece is probably RSS support which makes me sad. I can write a script to generate that from the list of article but I'm not sure if there's better way.
View source on this page: https://justine.lol/rss.xml
I got the template from a friend.
Very easy.
Using with the HTML 4.0 Transitional doctype? More like, I Blog with Raw Invalid HTML.
My HTML PageHello world!
Is technically "invalid", but it's "html" in the sense that everything from w3m and Netscape Navigator through to Chrome bleed will render it as intended.
(About to click the [reply] button hoping the HN software doesn't screw all that markup up.)
Browsers are, and HTML is on v5 and has deprecated things.
And using JS definitely can be deprecated too.
"Just raw HTML" is an odd statement when it's obviously not.
And the if some markdown and JS are ok, why not some CSS too?
If plaintext blogging fits your vibe and you’ve not yet heard of it, be sure to check out the gemini:// protocol. An overview of the protocol, proxied from Gemini to HTTP, available here: https://geminiprotocol.net/
See also this review/critique from the cURL author, especially if you’re going to implement it yourself. Particularly around certificate handling and URL parsing, there’s a lot of underacknowleded complexity in Gemini. https://daniel.haxx.se/blog/2023/05/28/the-gemini-protocol-s...