Blog Publisher v3: Markdown Fixed at the Source, Across 28 Posts
A stray asterisk where a heading should be, a code block bleeding into a paragraph, a list that never closes — small formatting bugs, but they land in front of every reader and quietly cost you credibility. The third version of my publishing tool was built to stop them at the source, and it cleared the problem across all 28 posts that carried it.
Why it kept breaking
The earlier versions converted content to HTML at the point of display, so rendering quirks only showed up once a piece was already live. The fix was the wrong shape: patching output instead of fixing the pipeline.
What v3 changed
- Clean at the source. Content is normalised and validated before it is ever stored, so what goes into the database is already correct.
- One reliable path. A single, tested conversion step replaced the ad-hoc handling that had grown up over time.
- Driven through an MCP tool. Publishing runs as a defined, repeatable operation rather than a manual ritual.
- Fail loudly, early. Malformed content is caught at publish time, not discovered by a reader.
The outcome
All 28 affected posts corrected at the source, and articles that render exactly as written from then on. A small tool fixing a real problem — done properly, so it stays fixed.
