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.
Current iteration of my blog is pure Elisp (org-publish). It is very simple. I like that I understand effectively whole thing bottom-up, and making any changes to machinery by advising Elisp is ridiculously easy. Being able to export the whole buffer with exact looks and feel of my Emacs theme is cherry-on-top. I like the overall feel of the thing, it has everything I need and nothing more.
My only gripe is that it is quite slow. My blog is pretty small, so having to wait on Emacs to build the whole thing is not fun. If my blog ever gets in the range of needing to compile hundred plus posts, I'll be seriously looking at alternatives. But until then, I get to enjoy just writing posts and exporting them with single keystroke.
As a long-time Emacs user, I also prefer Markdown (and by a wide margin). I have tried so many times over the years, even going all in for a time with Beorg on iOS. But I always come back to Markdown.
Part of it is that I just prefer the Markdown syntax to everything else, but the other part is that I just don't care to use much of the (admittedly super cool) machinery around org, such as task capture, calendars, etc.
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.
By that logic you don't even need wordpress complexity, you can just make static html pages out of any office text editor or any wyiwyg html editor (like seamonkey composer).
I use org-mode (mainly for vocabulary-building in English and other languages), but I steer clear of its complicated html-compiling functions, as I have a hard time remembering all the different options and keybindings.
I also prefer Elixir to Gleam, but I still think this is a pretty neat setup!
> The reason being that Orgmode is a far superior format [to markdown]
I have to disagree with this. I will admit there are some things org mode does better than markdown, but there are also things it does worse. And probably the biggest is alluded to in the rest of that sentence: "[the] only downside is that you have to be inside Emacs to fully enjoy."
A while ago, I read a blog post about how orgmode was better than markdown[1], that got me interested enough to try it out with neovim[2] using the nvim-orgmode[3] plugin. Admittedly, some of my issues were bugs or missing features in that plugin. But, at least in my opinion, orgmode is just as flawed as markdown, even in some of the same ways. Some of the issues are:
- like the original markdown it isn't precisely specified so there are ambiguities in the description of the synatax, and the definitive specification is just the emacs implementation.
- while it is more consistent than markdown in some ways, it is also less consistent in other ways
- it is designed for, well, organizational tasks, so while it is well suited for things like todo lists and agendas, it isn't quite as well suited for things like writing a blog post
- probably the one that frustrated me the most is there are cases where it is quite clunky and/or difficult to express something. For example, if you put a "$" in an inline code object, in some cases that will be parsed as the start of LaTeX inline math object, especially if you have two "$"s. And from what I can tell, the standard way to work around that is to use a zero-width space in the right place.
Would I say that org mode is strictly inferior to markdown? No. But I don't think it is strictly superior either.
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?
More byzantine that way
lol yeah this should just be a pile of elisp
Current iteration of my blog is pure Elisp (org-publish). It is very simple. I like that I understand effectively whole thing bottom-up, and making any changes to machinery by advising Elisp is ridiculously easy. Being able to export the whole buffer with exact looks and feel of my Emacs theme is cherry-on-top. I like the overall feel of the thing, it has everything I need and nothing more.
My only gripe is that it is quite slow. My blog is pretty small, so having to wait on Emacs to build the whole thing is not fun. If my blog ever gets in the range of needing to compile hundred plus posts, I'll be seriously looking at alternatives. But until then, I get to enjoy just writing posts and exporting them with single keystroke.
mine has no org-mode...which is fine...I like markdown:
find . -name '*.md' -type f -exec sh -c '
' sh {} +So simple, I love this.
As a long-time Emacs user, I also prefer Markdown (and by a wide margin). I have tried so many times over the years, even going all in for a time with Beorg on iOS. But I always come back to Markdown.
Part of it is that I just prefer the Markdown syntax to everything else, but the other part is that I just don't care to use much of the (admittedly super cool) machinery around org, such as task capture, calendars, etc.
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.
By that logic you don't even need wordpress complexity, you can just make static html pages out of any office text editor or any wyiwyg html editor (like seamonkey composer).
Ghost can take markdown files.
Write the .md in VsCode and use the ghost extension ?
I use org-mode (mainly for vocabulary-building in English and other languages), but I steer clear of its complicated html-compiling functions, as I have a hard time remembering all the different options and keybindings.
I also prefer Elixir to Gleam, but I still think this is a pretty neat setup!
Use https://dumindu.github.io/E25DX/ kind minimal theme or build a simple GoHugo theme and cut your tech-stack to 1 executable.
If you're reimplementing the wheel, at least do it in latest tech + minimal tech.
> The reason being that Orgmode is a far superior format [to markdown]
I have to disagree with this. I will admit there are some things org mode does better than markdown, but there are also things it does worse. And probably the biggest is alluded to in the rest of that sentence: "[the] only downside is that you have to be inside Emacs to fully enjoy."
A while ago, I read a blog post about how orgmode was better than markdown[1], that got me interested enough to try it out with neovim[2] using the nvim-orgmode[3] plugin. Admittedly, some of my issues were bugs or missing features in that plugin. But, at least in my opinion, orgmode is just as flawed as markdown, even in some of the same ways. Some of the issues are:
- like the original markdown it isn't precisely specified so there are ambiguities in the description of the synatax, and the definitive specification is just the emacs implementation.
- while it is more consistent than markdown in some ways, it is also less consistent in other ways
- it is designed for, well, organizational tasks, so while it is well suited for things like todo lists and agendas, it isn't quite as well suited for things like writing a blog post
- probably the one that frustrated me the most is there are cases where it is quite clunky and/or difficult to express something. For example, if you put a "$" in an inline code object, in some cases that will be parsed as the start of LaTeX inline math object, especially if you have two "$"s. And from what I can tell, the standard way to work around that is to use a zero-width space in the right place.
Would I say that org mode is strictly inferior to markdown? No. But I don't think it is strictly superior either.
[1]: I think it may have been https://karl-voit.at/2017/09/23/orgmode-as-markup-only/ but I'm not sure
[2]: I did use emacs for a few years, and still have a few emacs-like keybindings, but neovim is my preferred editor now.
[3]: https://github.com/nvim-orgmode/orgmode
Byzantine dotfiles
This better describes my NixOS config files! XD
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...
This is what I think of: https://rakhim.org/honestly-undefined/19/