# FlowDrop Office: a workflow you can watch URL: https://www.gxleano.com/flowdrop-office/ Date: 2026-11-17 Explaining an AI workflow is hard. In the editor you see nodes and edges. In the logs you see a list of jobs with ids and JSON. Both are fine for the person who built it. For everybody else, not really. So I tried something different. What if each node was a person at a desk, and you could watch the file move from one desk to the next? That is [FlowDrop Office](https://www.drupal.org/project/flowdrop_office). [Video: A pixel-art office replays a FlowDrop workflow: a message comes in, desks for security, writers and legal work on it one after another, and a draft comes out] *One brief, from the chat to the draft, walked desk by desk.* ## Where it comes from It started as a custom module in a demo site, for one workflow. After a day playing with it, it was clear that nothing in it was about that workflow. It reads the workflow you already have, so it works with any of them. Then it made sense to move it to drupal.org as a contrib module. I built it with the help of Claude. ## How it works (zero setup, promise) You do not configure anything. The office comes from the workflow itself: - Every caption node in the FlowDrop editor becomes an office, with the nodes on its right inside. - Every other node is a desk. The person at the desk shows what kind of node it is: a robot for AI nodes, a guard for guardrails, a dispatcher for gateways, a clerk for templates and text. - When a run is replayed, a clerk finishes at one desk and walks the file to the next one. The camera follows, and a subtitle says what the node did in plain words. Next to the scene there is an inspector. It tells each step with the real values of the run: what came in, what the node did and why, and what went out. The raw job output is still there for the people who want it. You can replay any of the last 12 runs, or send a new message from the chat on the page and watch that run. You can also star a run and keep it as a favorite. A favorite plays offline, without the pipeline, the AI provider or the network. (Favorites are stored in the workflow configuration, so they move to another site with a normal config export and import.) For a live demo this is my safety net. ## For people who never saw a workflow The plain view hides the node names and tells the run in seven stages: Receive, Safety, Understand, Search, Write, Review, Answer. Presentation mode puts the office full screen with the plain view on, and the arrow keys work from a presentation clicker. There is also a Record button. It replays the run and saves it as a video, so you can share it with somebody who does not have access to the site. ## Make your own scene (a hospital? a factory? a castle?) The office is only one way to draw a workflow. The drawing is a scene, and scenes are extensible: anybody can create a new one adapted to their needs. A module declares its scene in a `MODULE.flowdrop_office_scenes.yml` file, and its script registers it with `Drupal.flowdropOffice.registerScene()`. (The YAML keys and the scene contract are still internal, so they can change while the module grows.) The page then lets you switch between the scenes. The replay, the camera, the chat and the inspector stay the same. The scene only decides how the workflow looks. The module comes with two examples as submodules: a board, an isometric platform with one colored tile per section, and a town hall. So if a pixel-art office does not fit your team or your audience, you can draw something that does. ## Things I had to take in mind **Personal data.** A live turn runs in a FlowDrop session, and the session stores each message and sends it again as history on later turns. So a guardrail inside the workflow only sees the current message. To mask or refuse a message before it is stored, the module has one hook: `hook_flowdrop_office_turn_alter()`. **Big workflows.** An office with 40 desks is not readable. So offices are split at 16 desks, and steps that only pass the file on go by in a blink. If a replay would still take more than about a minute and a half, it plays faster. **Read-only.** The office only reads FlowDrop's own storage. The only thing it writes is the sessions of the live turns. ## Try it It needs Drupal 11.3 and [FlowDrop](https://www.drupal.org/project/flowdrop). There is no tagged release yet, so take in mind that things can still change. The [documentation](https://project.pages.drupalcode.org/flowdrop_office/) explains the installation and every part of the page. If you try it with your own workflows, let me know what do you think. The [issue queue](https://www.drupal.org/project/issues/flowdrop_office) is open. # Building this blog with spec-driven development URL: https://www.gxleano.com/building-this-blog/ Date: 2026-11-17 I wanted a personal blog for a long time. This time I built it the same way I build things at work: first the spec, then the code. In this post I explain how the project is organised, what changed on the way and what is still open. ## Decisions before code (the rule I break least) Every technical decision lives in a markdown file inside the repo, with a status: proposed, accepted, rejected or replaced. Nothing gets implemented without one. `specs/` ``` decisions/ 001-tech-stack.md 002-design-and-frontend.md 003-design-to-canvas.md 004-astro.md 005-ddev.md design/ brief.md components/ inventory.md ``` An accepted decision is not reopened. If new information appears, I write a new decision that replaces the old one. So the history stays in the repo, and I can see why something changed. > Change only what the current task requires. > > — My own rules for the agent ## I started with Drupal I work with Drupal every day, so the first plan was Drupal CMS with Canvas for the pages, on a small VPS. (Decisions 001, 002 and 003 are still in the repo, marked as partially replaced.) Then I reviewed it with honest numbers. The articles would be written in CKEditor, so Canvas was only useful for the home and a few pages. And the VPS was around 10 € per month, plus updates, backups and security. (yes, a Drupal developer picking Astro) At the end, the goal of this blog is to write, not to show Drupal. So decision 004 moved everything to Astro: a static site on Cloudflare, articles in MDX inside the repo, and my own components. The cost now is the domain, less than 1 € per month, and there is no server to maintain. A few hours later DDEV came back as the local environment (decision 005), because all my other projects use it and the ddev.com site already does the same with Astro. This is the part where the specs paid off. Changing the stack was one new file that replaced three, not a long discussion with myself. ## Plans and tasks For plans and tasks I use Strikethroo. A plan cites the decisions it depends on, gets split into tasks, and an agent executes them. Every task closes with its own check. (Plans live in `.ai/strikethroo/` and project knowledge in `.ai/kenkeep/`. The decisions stay in `specs/`.) So far the blog has five plans: `.ai/strikethroo/` ``` 01 astro-blog-setup 02 design-c-components 03 media-years-and-test-content 04 benji-style-annotations-and-doodles 05 production-launch-readiness ``` The code is written by Claude Code from the plans. I review every change in the browser, in light and dark, before it gets committed. ## From design to code The design started with a brief: what the blog should feel like, not how to draw it. Short and direct like the way I write, no hero images, no card grids, links that look like links. The reference was [benji.org](https://benji.org). I took its principles (a narrow reading column, a lot of white space, notes in the margin) but not its look. Claude Design gave me three directions and I picked the third one, "Margins". Brief → Claude Design → Component inventory → Plan → Astro component *From a brief to a page made of components.* The approved design was split into an inventory of components, and each plan built a part of it. The fonts are Spectral for the text, Bricolage Grotesque for titles, JetBrains Mono for code and dates, and Reenie Beanie for the notes in the margin. ## The handwritten notes The notes are the signature of the blog: margin notes, side notes, highlights and the odd doodle. Each one is drawn once, the first time it scrolls into view, and then it stays. They are real text, not images, so they can be read, translated and selected. If you prefer reduced motion, nothing animates and the notes are just there. To be honest, the handwriting is not mine yet. Reenie Beanie is a placeholder until I turn my own handwriting into a font. ## What is next Before launching, the last plan prepares the site for production: CI, RSS, a sitemap, a 404 page, meta tags for search and social, and an `llms.txt` with Markdown copies of the articles for AI agents. After that, the font with my handwriting. And then the important part: write. If you have any feedback about the blog or about this way of working, just let me know. # The pieces of this blog URL: https://www.gxleano.com/kitchen-sink/ Date: 2026-11-17 This post is a bit different. It is not about a topic: it shows the pieces I have to write here, one by one. If you are building your own blog, maybe some of them give you ideas. For me it is also the page I open every time I change something in the design, in light and dark, wide and narrow. ## Text and inline styles Most of a post is just text. A [link](https://www.gxleano.com/), some `inline code` for machine names, and now and then a highlighted phrase or a hand underline for the few words that really matter. Both are drawn once, the first time you see them. ### Lists A list when there are really several items: - First item, short. - Second item, long enough to wrap onto a second line, so the indent and the line height still read well on a phone. - Third item. And a numbered one when the order matters: 1. Write the draft. 2. Read it out loud. 3. Cut a third of it. ## Margin notes (plain: text only) A margin note is a comment I write on the side, like in a notebook. On wide screens it sits in the right margin; on a phone it goes above the paragraph. (arrow: points at the text) It can point at the paragraph with a hand-drawn arrow. (bracket: groups lines) Or group several lines with a bracket, when the comment is about the whole paragraph and not only one sentence. ## Sidenotes and footnotes A sidenote is a short clarification right where it is needed. (Like this one: it sits in the margin on wide screens and under the line on a phone.) They are numbered in order. (This is the second one.) For longer asides there are classic footnotes at the end of the post.[^1] ## Images [Image: Flat green mountains under a pale sky with a light sun] *An image with the caption in the margin.* Images sit on a calm surface, and the caption goes in the margin or below. Both images here are placeholders. [Image: A pale green card with a round avatar and two lines of text] *A portrait image with the caption below.* ## Video A clip behaves like a GIF: it plays by itself, muted and in a loop, with a small pause button. If your system asks for reduced motion, it starts paused. [Video: A green dot moving over a line] *A clip: autoplay, muted, loop.* When the video needs your attention, it is a normal player with controls. [Video: A green dot moving over a line, with controls] *A player: native controls, no autoplay.* ## Quote > Make it work, then make it plain. > > — A note to myself ## Code Code with a filename, when the file matters: `src/lib/hello.ts` ```ts export function hello(name: string): string { return `Hello, ${name}`; } ``` And a plain block for commands: ``` $ ddev npm run build build finished ``` ## Doodles You have probably seen a rocket and a planet in the margins of this post. Doodles are small drawings I can put next to the text. They only show when there is room, so on a phone you do not see them. That is every piece. If you want to see how they are built, the blog is made with Astro, and I wrote about the process in [Building this blog with spec-driven development](https://www.gxleano.com/building-this-blog/). [^1]: Like this one. Footnotes are for the asides that would break the reading if they were in the margin.