introducing
jouissance
After looking at and trying too many blogging tools, many of which aren’t all that happy in a shared space like ours, I did what some in ’26 who aren’t 10× developers might try, I gave a 132-word prompt to a chatbot for its LLM to triangulate to a tool, a tool that fit my criteria better. I have good friends in both camps — strongly anti-AI and those who enthusiastically use these tools, even pay for them.
I am on the fence and consequently will not release it in the usual way. You’re free to use the executable. Further detail about sharing the source hasn’t been thought through.
technically
It’s simple — so simple I don’t think it needs any doc.
Nonetheless, I’ll say this much:
- run as
/home/whir/bin/blog - It’s easy to play with, blow away, begin again. The learning curve should be quick and nearly painless. Please let me know either way
- It doesn’t do all Markdown. Tables, footnotes, math and strikethrough (at least) are not supported
- nearly 7× smaller than Zola
The only gotcha is you are free to “misalign” web space and file space. It does not fail safe. If line 3 and 4 in ~/.blog/config are
url = http://tilde.club/~ford/p3
out = /home/ford/public_html/a/b/c/d
you will not find your blog at that URL, it will 404.
extruded from the LLM
I haven’t tested these.
Slugs and URLs: the slug is fixed when you create the post, so editing the title doesn’t move the URL. Renaming a file to change its date or slug creates a page at the new URL and leaves the old page in place, so unpublish with p first.
Images: drop them into the output directory under the post’s slug, for example public_html/blog/my-post/pic.jpg, and reference them as . Unpublishing or deleting a post leaves them there.
Stylesheet and raw HTML: style.css is written once and never overwritten, so edit it freely. Raw HTML in posts passes through unescaped.
Config changes: after editing ~/.blog/config or style.css, press r to rewrite every page, as the status line shows.
p.s. I’m not a developer at all.