I mentioned org-publish late in the post, I do have my own personal blog built atop of it (and nix as well), this current setup with Gleam is more like an experiment and I get a lot of stuff for free that took me a while to get it working in my personal blog (like syntax highlighting, rss, etc), and I'd still argue that my templating system in pure elisp + crappy html sucks.
I prefer to write words not code. I use WordPress because it hides all the complexity and lets me just write instead of messing with Markdown (or an entire separate system), CI pipelines, custom markup hacks for page features, Emacs cruft, etc..
Yeah WordPress is a security nightmare, but Ghost's editor sucks and there's no viable open-source alternatives with modern security and features.
Someone who spends his day in emacs writing code and org-mode for work will have the muscle-memory and lisp knowledge to make emacs and org-mode as easy for him as WordPress is for you.
I've been subscribed to a mailing list for many years, of which perhaps half I actively participated in the mailing list. Almost the entire time I used alpine, a terminal mail client, hosted on a remote server, getting its mail from and sending it through gmail. A stupid setup, perhaps, but it was productive, and I wrote. Since giving up that setup (I wiped and repurposed the server) and trying to use gmail's web interface or Mac's mail application, I've been silent. So, I understand the author's desire for a setup that might seem arcane or byzantine: sometimes there's something about such a system that is comfortable and keeps you writing.
People using Emacs who prefer to write words already are writing them in org mode. For them, switching to Wordpress means having to use a different system to write words.
The whole export, pipeline, publish, etc is precisely so they can continue to write just words. Once you've got a setup you like, you stop fiddling and just type.
My own org mode flow has been stable for almost 7 years. I just add an entry to my org mode file, and with a few commands (or recipe), have it up on the site.
I don't understand why gleam and pandoc are in there. Org-mode can already generate HTML. A little bit of Emacs Lisp turns it into a blogging engine.
https://ahungry.com/blog/2013-04-01-blogging-with-org-mode.h...
I mentioned org-publish late in the post, I do have my own personal blog built atop of it (and nix as well), this current setup with Gleam is more like an experiment and I get a lot of stuff for free that took me a while to get it working in my personal blog (like syntax highlighting, rss, etc), and I'd still argue that my templating system in pure elisp + crappy html sucks.
Probably because they wanted... to?
lol yeah this should just be a pile of elisp
I prefer to write words not code. I use WordPress because it hides all the complexity and lets me just write instead of messing with Markdown (or an entire separate system), CI pipelines, custom markup hacks for page features, Emacs cruft, etc..
Yeah WordPress is a security nightmare, but Ghost's editor sucks and there's no viable open-source alternatives with modern security and features.
Someone who spends his day in emacs writing code and org-mode for work will have the muscle-memory and lisp knowledge to make emacs and org-mode as easy for him as WordPress is for you.
I've been subscribed to a mailing list for many years, of which perhaps half I actively participated in the mailing list. Almost the entire time I used alpine, a terminal mail client, hosted on a remote server, getting its mail from and sending it through gmail. A stupid setup, perhaps, but it was productive, and I wrote. Since giving up that setup (I wiped and repurposed the server) and trying to use gmail's web interface or Mac's mail application, I've been silent. So, I understand the author's desire for a setup that might seem arcane or byzantine: sometimes there's something about such a system that is comfortable and keeps you writing.
People using Emacs who prefer to write words already are writing them in org mode. For them, switching to Wordpress means having to use a different system to write words.
The whole export, pipeline, publish, etc is precisely so they can continue to write just words. Once you've got a setup you like, you stop fiddling and just type.
My own org mode flow has been stable for almost 7 years. I just add an entry to my org mode file, and with a few commands (or recipe), have it up on the site.
mine has no org-mode...which is fine...I like markdown:
find . -name '*.md' -type f -exec sh -c '
' sh {} +This is a classic bell-curve meme. The midwit gets lost in complex setups, but the smartest approach is simply to write, regardless of the platform.
https://muratbuffalo.blogspot.com/2026/03/800th-blog-post-wr...