I ship focused, testable fixes in open-source UI projects, currently concentrating on zimme-zoom and drawnix.
These are maintained tools, not claims to cover every use case. Each project states what it does, what it leaves out, and where help is useful.
Local-first React/Canvas whiteboard for offline drawing and note taking. The project focuses on privacy, browser availability, and readable implementation rather than collaboration or cloud sync.
Self-hosted journaling and archive app. The useful core is simple: keep notes, attachments, and personal records on a server you control, then serve the web client from the same origin.
Small upstream fixes in projects I actually read: accessibility behavior, test coverage, CI guardrails, type contracts, and bug paths that maintainers can review without a rewrite.
Learn from established projects without presenting shared interaction patterns as original invention.
Local-first tools should not imply cloud collaboration, and experiments should not be marketed as finished products.
Upstream contributions start with a reproducible problem and stay small enough to review carefully.
Test gaps, lint baselines, and known limitations belong in the record instead of behind broad claims.
Only merged work appears here. The useful evidence is the problem, the review trail, and the regression coverage.
Added named bundle budgets for the public barrel and the Image-only import path, then followed through review, Node 20 compatibility, and documentation cleanup until merge.
Moved the viewer into a body portal, hid background content while open, restored focus safely, and answered every review thread with targeted regression coverage.
Kept the pan gesture available while freehand tools are active, with interaction coverage refined through two maintainer reviews.
Moved heading-level publication into plugin initialization so Markdown shortcuts use the configured levels from their first render.
A Chinese engineering note on a small dependency surface, local-first boundaries, and respectful attribution.
Read the Chinese noteFuture notes will cover review follow-up, Canvas input bugs, test debt, and decisions that changed after maintainer feedback.
Repositories