TL;DR
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
Byzantine Systems has published a post describing how its blog turns Emacs Org-mode documents into a site using Pandoc and a small Gleam and Blogatto pipeline. The author says the setup keeps writing, code, citations and diagrams together while using Nix to manage the build environment; the post does not report performance tests or compare the workflow with alternatives.
Byzantine Systems has published a technical post detailing a blog workflow that starts with Org-mode files written in Emacs and uses Pandoc, Gleam and Blogatto to produce a website. The post matters to developers and writers weighing how to keep authoring tools flexible while making the publishing pipeline understandable and repeatable.
The workflow described in the post keeps the author’s direct interaction focused on Org documents. Pandoc converts the Org source into Markdown, which Blogatto then uses to generate the site’s HTML. The author describes Gleam as the language for a small, typed static-site pipeline and Lustre as the means of defining HTML around the generated posts without adding a separate template language.
The post illustrates that approach with a post-index function written in Gleam. It sorts posts by date, displays an empty-state message when there are no posts, and otherwise renders a list of post links. The author presents this as ordinary, type-checked code rather than a template file. That example shows one concrete role for Gleam in the setup; it does not establish that the workflow is faster or safer than other site generators.
Other tools fill specific roles: d2 creates declarative diagrams, while Org Babel can run source blocks within documents. The author says the diagrams can be generated from code embedded in the writing workflow. Nix, flakes and devenv are used to pin the build environment. The post’s summary is that Nix makes the rest of the pipeline “pleasantly uneventful,” an assessment from the author rather than an independently measured result.
Keeping Writing and Publishing Together
The development is a practical example for people who want a plain-text authoring format but need more than basic prose in their publishing process. The author describes writing code, working with BibTeX citations and generating diagrams as parts of the same activity. Keeping those elements in Org-mode may reduce the need to move between separate applications, though the post offers a personal account rather than evidence that every writer would benefit from the arrangement.
The separation between source and output also matters. Org-mode is the authoring format, Markdown is an intermediate format, and Blogatto handles site generation. This means the author can use Org-specific features without requiring the site generator to consume Org directly. Gleam and Lustre provide a code-based way to build site elements such as the post listing, while Nix is intended to make the build inputs more consistent.
For readers considering a similar setup, the article gives a useful map of how the parts connect. It also makes the tradeoff visible: Org-mode’s richer authoring features are most accessible inside Emacs, while the multi-tool pipeline asks users to configure and maintain several components.
As an affiliate, we earn on qualifying purchases.
From Org Source to Site
The post introduces the workflow as the first entry on the Byzantine Systems blog. Its author says this is not their first attempt at building a site around Org-mode. A previous personal-blog setup also used Emacs, scripts and Nix; the new effort aims to keep writing in Emacs while making the publishing side smaller, typed and easier to understand.
The article contrasts Org-mode with Markdown. It acknowledges that Markdown is widely readable and supported by static-site tools, and says the published site uses Markdown produced by Pandoc. The author’s preference for Org-mode rests on its support for source blocks, export targets and mixed computational and natural-language documents. That preference is the author’s judgment, not a general finding that Org-mode is superior for every project.
The source also invokes arguments about Emacs and the Unix principle of tools that do one thing well. The author favors having a unified writing environment for work that includes prose, code, diagrams and references. The post does not claim that Emacs is a universally suitable choice; it explains why this particular writer prefers to keep those tasks together.
As an affiliate, we earn on qualifying purchases.
What the Post Does Not Measure
The article is a description of one author’s setup, not a controlled comparison of static-site workflows. It supplies no build-time benchmarks, maintenance figures or independent evaluation of the tools. It also does not establish how the pipeline would perform for a larger publication or how much configuration is needed for another user to reproduce it.
The supplied source does not state the post’s publication date, and it does not provide a complete installation guide or a full account of every build step. It is therefore unclear from this material how the tools are configured together in detail, what limitations the author encountered, or whether the workflow has changed since publication.
As an affiliate, we earn on qualifying purchases.
The Workflow’s Next Steps
The post presents the pipeline as an experiment and says the author’s longer-term aim is to bring more of the work inside Emacs. It does not give a timetable for that change or name a specific next release or feature. Readers interested in adopting the setup would need to consult the original Byzantine Systems post for its linked examples and determine whether the described tools fit their own publishing needs.
For now, the confirmed development is the publication of the technical account itself. Further practical evidence—such as updates to the build, a reproducible setup guide or experience maintaining the site over time—would clarify how well the approach works beyond the author’s initial description.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the blogging workflow described?
The author writes in Emacs Org-mode, uses Pandoc to convert Org files to Markdown, and uses Blogatto to generate the site. Gleam and Lustre are used for typed site code and HTML elements.
Why does the author write in Org-mode instead of Markdown?
The author values Org-mode’s ability to combine prose with source blocks, citations and generated diagrams. Markdown is still part of the publishing pipeline, but Pandoc produces it from the Org source.
What does Gleam do in the setup?
Gleam is used for parts of the static-site pipeline. The post demonstrates a type-checked function that sorts posts and renders a list of links or an empty-state message.
Does the article show that this workflow is better or faster?
No. It describes the author’s preferred setup but gives no benchmarks or comparative results. The stated benefits are the author’s reasons for choosing the tools, not independently verified performance claims.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
