{"slug": "a-repeatable-workflow-for-paper-figures-so-you-stop-redrawing-them-every", "title": "A repeatable workflow for paper figures so you stop redrawing them every revision", "summary": "A developer has created a repeatable workflow for scientific paper figures that treats them as regenerable code rather than hand-crafted vector files. The process involves writing figure descriptions as plain text in a repository, feeding them into an AI tool to generate editable vector drafts, and storing the source description so revisions become simple text diffs rather than full rebuilds. This approach reduces figure revision time from an afternoon to roughly twenty minutes.", "body_md": "If you've shipped a paper, you know the figure tax: you build a beautiful schematic, a reviewer asks you to move one box, and you spend an afternoon re-aligning everything by hand. Do that across three revisions and you've spent more time nudging vectors than running the analysis.\n\nI started treating figures the way I treat code: as something that should be **regenerable from a source**, not hand-crafted once and patched forever. Here's the workflow that stuck.\n\nBefore opening any drawing tool, I write the figure as a plain description in the repo:\n\n``` php\nligand -> receptor (binding)\nreceptor -> kinase (activation)\nkinase -> targetA, targetB (phosphorylation)\ntargetA -| receptor (inhibition, feedback)\n```\n\nThis forces the logic to be explicit. If you can't write the relationships down cleanly, the figure isn't ready — and that's a science problem, not a drawing problem.\n\nI feed that description into a tool that will [create scientific figures with AI](https://figcanvas.com/) and get a laid-out first draft. The point isn't \"AI does my figure.\" The point is the boring geometry — consistent boxes, even spacing, arrow routing — is done before I start, so my time goes into the parts that need judgment.\n\nThe non-negotiable: the result has to be **editable vector**, not a flattened PNG. When the reviewer asks to move a box, I move a box. When a journal wants a different size, it scales without turning into mush.\n\nBecause the source description lives in the repo, \"revision 2\" is a diff, not a rebuild. I change the text, regenerate, fix the few labels that matter, export. Twenty minutes instead of an afternoon.\n\nIt won't make a bad figure good — encoding, color logic, and what you choose to show are still on you. And the first draft always needs cleanup; anyone promising one-click publication figures is selling something.\n\nBut moving the *source of truth* from \"a fragile vector file\" to \"a text description plus a generator\" changed figures from a dreaded last step into something I can iterate on as fast as I iterate on the writing.\n\nHow do you handle figure revisions? Still hand-editing in Illustrator, or have you found a more reproducible setup?", "url": "https://wpnews.pro/news/a-repeatable-workflow-for-paper-figures-so-you-stop-redrawing-them-every", "canonical_source": "https://dev.to/figcanvas/a-repeatable-workflow-for-paper-figures-so-you-stop-redrawing-them-every-revision-482h", "published_at": "2026-05-31 02:24:15+00:00", "updated_at": "2026-05-31 02:41:39.457863+00:00", "lang": "en", "topics": ["ai-tools", "generative-ai"], "entities": ["FigCanvas"], "alternates": {"html": "https://wpnews.pro/news/a-repeatable-workflow-for-paper-figures-so-you-stop-redrawing-them-every", "markdown": "https://wpnews.pro/news/a-repeatable-workflow-for-paper-figures-so-you-stop-redrawing-them-every.md", "text": "https://wpnews.pro/news/a-repeatable-workflow-for-paper-figures-so-you-stop-redrawing-them-every.txt", "jsonld": "https://wpnews.pro/news/a-repeatable-workflow-for-paper-figures-so-you-stop-redrawing-them-every.jsonld"}}