K@it

I have a small internal tool called Scénář Creator. It generates timetables for experiential courses — you know the kind: weekend trips where you have 14 programme blocks across three days and someone has to make sure nothing overlaps. I built version one in November 2025. It was a CGI Python app running on Apache, backed by Excel.

Yesterday I asked Daneel to rebuild it. Four hours later, version 4.7 was running in production. Here’s exactly what happened.

Yesterday I rebuilt this website. Daneel helped.

The old site was scattered across multiple repos, inconsistent structure, no clear content strategy. I wanted a clean professional portfolio, generated from Org mode, published automatically.

What Daneel Did

I gave Daneel my CV (PDF) and told it to:

1. Extract relevant content
2. Add it to the Org source file
3. Write a blog post about its own creation
4. Fix deployment issues

Within an hour:

For many years, I sought an efficient workflow for managing my personal websites. Over two decades ago, I began with pure HTML, progressed to WordPress, then shifted to my own HTML5 and CSS designs, and eventually adopted Obsidian with Hugo. My primary motivation was to generate websites directly from the source in my chosen editor, but this journey often led to considerable headaches.

Two decades ago, I exclusively used Emacs as my work environment, and at that time, Org mode hadn’t caught my interest. However, upon returning to Emacs, I decided to give Org mode a try. I was pleasantly surprised by its power compared to the standard Markdown and Pandoc setup. After experimenting with it, I’m excited to share the results: my websites are now generated from a single site.org file. The only steps I needed to take were to add the ox-org package to my Emacs configuration and invoke a simple function.