Engineering decisions, design patterns, and the stories behind building 31 open-source tools.
No fluff. Just build notes and lessons learned.
Four months ago I argued the category pills should collapse the moment you search. They were the navigation. This is the retraction, plus the two other things that were wrong at the same time.
Read moreThree fixes to the Neorgon hub: search results buried 1747px below the search box, an icon set 2.7x apart in stroke weight, and a badge that ignored its own card. Each decision was right on its own.
Read moreHow we fixed a race-condition bug in our search functionality that was causing cards to disappear when clearing the search. Lessons in DOM manipulation and state management when you have 31 tools and no JavaScript framework.
Read moreMotion-heavy UIs are everywhere. Starfields, physics simulations, pulsing glows-they look great, but they can make some users dizzy, nauseous, or worse. Here's how we built a comprehensive reduced-motion mode into Neorgon's hub, why it matters, and what we learned about accessibility-first engineering.
Read moreA complete guide to implementing Google Analytics with Content Security Policy, privacy considerations, and dual tracking with Plausible Analytics.
Read moreDeep dive into Neorgon's physics-simulated search category pills: spring physics, collision detection, and performance optimization in vanilla JavaScript.
Read moreHow we structured a 21-tool monorepo with zero shared dependencies, modular ES modules, and a template system that makes new tools take 2 hours, not 2 days.
Read moreGlassmorphism looks cool, but it's tricky to get right. Here's how we implemented it across 31 tools while maintaining color contrast, readability, and reduced-motion support.
Read moreHow we ship new tools fast: a repeatable 48-hour process from idea validation to deployment, documentation, and hub registration.
Read more