I wanted a content workflow that felt less like operating a CMS and more like briefing a capable assistant. So that is what I set up. I can message Hermy in Discord, explain the article I want, dump context, tighten the angle, and let that conversation become something website-ready.
The important bit is that I am not filling out a dozen forms or bouncing between notes, docs, and publishing tools. I am having a conversation. Hermy acts like a personal editorial assistant for the blog: listen carefully, structure what matters, draft the piece from the discussion, and then publish it to Bloomindesign.
Part 1 of 3 in the Bloomindesign Hermy workflow series. After this, read Part 2 on the development cycle and Part 3 on image creation.
This is a trial run rather than a finished product. The core workflow already works, and the next iterations will add things like tone-of-voice presets, richer editorial controls, and more image-generation options.
The workflow at a glance
How the Hermy article workflow works
A cleaner version of the chat → brief → draft → review → publish flow.
Same workflow, just without the decorative faffing about: conversation first, structure second, drafting third, review fourth, and publishing last. The point is not to automate taste out of the process. The point is to make the admin fade into the background so I can focus on the article itself.
What Hermy is actually doing
Step 1: Step 1: I talk to Hermy in Discord
This starts the most human way possible: I explain what I want the article to say. That can include the core idea, who it is for, rough phrasing, examples I want included, objections I want handled, and what tone I am aiming for.
In practice, this feels much closer to briefing a trusted assistant than prompting a faceless text box. I can be messy. I can ramble. I can correct myself. That is useful, because real article ideas rarely show up fully formed and wearing a tie.
Step 2: Step 2: Hermy turns the conversation into a real editorial brief
Once there is enough context, Hermy can infer the article structure: the main thesis, the likely headline, the supporting sections, the examples worth keeping, and the bits of fluff that deserve to be launched into the sea.
That means the conversation becomes a usable outline instead of a giant chat log. The brief is no longer trapped in my head or buried in Discord messages. It becomes something that can actually drive a polished article.
Step 3: Step 3: The draft gets written with the chosen model
This workflow also matters because it separates orchestration from the drafting engine. Hermy can coordinate the process while I choose the model I want involved in the writing step. Right now, this specific experiment uses Codex.
That flexibility matters. Sometimes I may want one model for speed, another for voice, and another for editing. The workflow should not care. Hermy should make the system usable while the underlying model changes depending on the job.
Step 4: Step 4: I keep editing through conversation
A draft is not the finish line. It is the first version worth reacting to. The next step is more conversation: tighten this point, make that section punchier, remove the waffle, add an example, sharpen the intro, soften the salesy bit, and keep going until it sounds like something I actually want my name on.
That is where the assistant framing really helps. I am not restarting from scratch every time. I am steering. Hermy keeps the context, updates the article, and absorbs the fiddly work that usually turns writing into admin.
Step 5: Step 5: Hermy publishes it to the website
Once the content is approved, Hermy can push the article into the Bloomindesign site itself. That includes the written post, supporting imagery, and the mechanics needed to make the page live. So the workflow does not stop at “here is your draft, good luck.” It actually finishes the job.
That matters because the biggest killer of content momentum is usually not writing. It is the nonsense surrounding writing: formatting, asset wrangling, page updates, previews, and all the tiny bits of friction that make an article somehow take all afternoon.
Why I like this workflow
The whole point is that this setup behaves like an actual assistant relationship. I bring the ideas, priorities, and judgement. Hermy handles the translation layer between conversation and execution. That makes it easier to produce articles without turning the process into a ceremony.
It is also a nice middle ground between doing everything manually and pretending one-click content generation magically produces something good. The human part stays in the loop where it belongs. The repetitive part gets delegated. Lovely. Civilised, even.
What comes next
This is the early version of the workflow, not the final form. The next additions are obvious: tone-of-voice controls, better drafting modes, richer image-generation support, and more reusable publishing patterns so different kinds of posts can be produced with less effort.
For this article, I rebuilt the banner image by starting with a robot from my Obsidian image library and using Nano-banana-2 to turn it into a cleaner black-and-white editorial banner. That is exactly the kind of thing I want more of: discuss the concept, generate the assets, write the article, and publish the finished result from the same conversational workflow.
Read the full series
Three articles, one system: conversation, development cycle, then image workflow.