Progress notes and build logs from the personal projects I am working on. What I am shipping, what broke, and what I learned along the way.
These are my devlogs: ongoing write-ups about the side projects and experiments I build in my own time. Expect decisions, tradeoffs, dead ends, and the occasional win, documented as the work happens. Use the search to jump to a project or filter by category.
How my Figma to code plugin turns several frames of one page into a single responsive HTML file: name-matched merging, mobile-first breakpoints read from the frame widths, and a mixed-text bug that shipped invisible numbers.
How I added a Tailwind mode to my Figma to code plugin: a v4 browser CDN, faithful arbitrary-value utilities, and a flexbox shrink bug that only Tailwind surfaced.
The second pass on my Figma to code plugin: real HTML tags chosen without AI, mixed text as spans, and sections that reach the screen edges.
How I built Design to HTML, a Figma plugin that turns a selected frame into clean HTML and CSS, and the per-side border bug that taught me to read Figma's stroke model properly.
I ported my ImageMagick VS Code extension to Obsidian. The port removed about 700 lines, and then a rotate slider that would not slide taught me where the real cost was hiding.
A cleanup release for my ImageMagick VS Code extension. No new features, 98 fewer lines, and one real bug that fell out when I deleted the code that was hiding it.
0.4.0 of my ImageMagick VS Code extension adds saved optimization presets and a one-click optimize from the Explorer, encoded in the extension host with no panel and no uploads.
The 0.3.0 release of my ImageMagick VS Code extension fixes drag-and-drop from the Explorer, plus what is coming next.
How I built SafiCSS, a tiny runtime CSS-in-JS library for plain HTML that turns a style object into a class name, with no build step.
Cleaning up vault-crm's Obsidian community review warnings, a dependency override that was quietly broken, and a release that failed on the wrong lockfile.
How I built S-Calc, an Obsidian plugin that evaluates each line of an s-calc code block and prints the answer inline in your theme accent colour. The build story: the engine, live currency, the CodeMirror editor layer, and the 0.6.0 release.
How I built an open take on closed site auditors: 93 checks across 15 categories, a fast crawler, a themed HTML report, and an npm SDK. One runtime dependency at the core.
A minimal Chrome extension that shares the current page to 10 networks or copies it as a blog-ready Markdown snippet, built on just activeTab and scripting so it never touches your browsing history.
Part 2: building the client's lead automation in n8n, wiring automatic email delivery and a Listmonk newsletter sync with double opt-in, then self-hosting it live on their own server.
Part 1 of building a client's LinkedIn lead automation: what the project set out to do, and the information and secure access I gathered before writing any of it.
Build logs and progress notes from my personal projects. Each post tracks what I am working on, the decisions I made, what broke, and what I learned. They are written as the work happens, not polished after the fact.
Whenever a project moves far enough to be worth a write-up. There is no fixed schedule; the cadence follows the work.
Yes. The blog is tutorials and deep-dives meant to teach. Devlogs are running journals of projects in progress, closer to building in public than a finished guide.
Reach out through the contact page. If a project is open to feedback or collaboration, I will say so in the post.