https://blog.without.hosting/tags/ghostwriter/Recent content in Ghostwriter on Without hostingHugo -- gohugo.ioen-USSun, 07 Jun 2026 15:20:00 +0000https://blog.without.hosting/posts/write-fast-publish-fast-still-iterating/Sun, 07 Jun 2026 15:20:00 +0000https://blog.without.hosting/posts/write-fast-publish-fast-still-iterating/<p>My blog <a href="https://blog.without.hosting/posts/a-bot-to-help-me-blog/">has a ghostwriter</a>. The bot writes drafts, tightens paragraphs, fixes typos, commits them. That works well.</p> <p>It also creates an interesting constraint: because the LLM can turn a ramble into something readable in minutes, the post is often ready to publish long before the dev task it documents is actually finished. You want to publish early — the writing is there, readers can engage — but you are still iterating on the thing the post is about. The article will change as the work progresses.</p>https://blog.without.hosting/posts/a-bot-to-help-me-blog/Wed, 03 Jun 2026 10:04:39 +0000https://blog.without.hosting/posts/a-bot-to-help-me-blog/<p>I built a Telegram bot that can write and edit my blog posts but cannot publish them. Hugo <code>draft: true</code> is enforced by the tool, not trusted to my discipline.</p> <p>The bot reads and writes files in the Hugo repo directly. No separate editorial database — the Markdown files are the source of truth. When a diff would flip <code>draft: true</code> to <code>draft: false</code>, the commit script refuses. There is an override (<code>ALLOW_PUBLISH=1</code>) but the bot cannot set it. Only I can, at a terminal.</p>