BACK_TO_FEEDAICRIER_2
Excalidraw fork automates blog diagram exports
OPEN_SOURCE ↗
HN · HACKER_NEWS// 12d agoTUTORIAL

Excalidraw fork automates blog diagram exports

Martin Lysk shows a practical Excalidraw workflow for technical blogging: wrap the elements you want in a frame, name the frame with an export prefix, and let a forked VS Code extension emit matching light and dark SVGs automatically. The payoff is a much tighter edit-preview loop than hand-exporting diagrams every time you tweak a post.

// ANALYSIS

This is the kind of niche automation AI coding is actually good at: spotting a repetitive annoyance and turning it into a tiny local tool. The big idea here is not Excalidraw itself, it’s collapsing export friction into a naming convention.

  • The first GitHub Action proved the concept, but it pushed the feedback loop into CI and broke down on ARM Macs.
  • Local auto-export keeps blog assets co-located with the `.excalidraw` source, so preview stays honest while you write.
  • `export_` as a frame prefix is a clean little API: intent lives in the filename, not in a separate settings panel.
  • Separate light and dark SVGs solve a real publishing problem for theme-aware blogs without extra manual steps.
  • Release artifacts make the fork easy to try, which matters when the whole point is reducing one person's publishing friction.
// TAGS
excalidrawideautomationopen-sourcedevtool

DISCOVERED

12d ago

2026-03-30

PUBLISHED

13d ago

2026-03-30

RELEVANCE

5/ 10

AUTHOR

mlysk