← All projects

Infographic Pipeline

Turned-on monitoring screen
Photo by Stephen Dawson on Unsplash

I got tired of hand-redrawing the same diagram every time the underlying data changed, so I started building Infographic Pipeline to fix that once instead of every time. Every book and article I write ends up needing charts and infographics, and for a long time that meant opening a design tool and manually rebuilding a chart from scratch whenever a number moved — work that added nothing to the writing itself.

Where it stands today: I'm building the generator implementations out one worker at a time — separate workers for raw SVG, Mermaid, draw.io XML, and Syncfusion output — and verifying each one against real content from the books I'm actually writing, rather than synthetic test cases that would tell me less about whether it actually works. Right now I'm chasing down a draw.io WebView rendering defect before I call that phase done; I'd rather say it's still in progress than round up.

Where it's heading is a pipeline that turns structured content — outlines, data points, diagram specs — into publication-quality SVG infographics for books and articles, so the underlying data can change without anyone needing to redraw the chart by hand. That's still ahead of me, not behind me, but the piece of it I can already point to — real generator workers, verified against real book content — is the part that gives me confidence the rest is reachable.

flowchart TD
    Content["Structured content\n(outlines, data points,\ndiagram specs)"] --> Generator["Generator\n(in progress, one\ndiagram type at a time)"]
    Generator --> Verify["Verified against\nreal book content"]
    Verify --> SVG["Publication-quality SVG"]

Want to know more?

Interested in "Infographic Pipeline"? Leave your details and I'll follow up with more information.

← All projects