Collaborations
Track a collaboration request without losing it in an inbox.
Collaboration requests arrived through email, social media, and GitHub issues with no unified way to track or evaluate them.
A public prototype demonstrates the interaction; scope and data are intentionally limited.
Case Study
Before
Collaboration requests came through email, social media and GitHub issues with no one place to note and follow them.
After
Collaborations on the App shell: keep collaboration requests and their status together in one searchable list.
How it's solved
Built a local notebook where you add a request with a title and details, set its status (Draft, Open, Active, Done), filter by status from the sidebar, search it and remove it with Undo. Entries are stored in this browser's localStorage.
Trade-offs
No backend, submission form or matching — entries stay in this browser.
Related Articles
Further reading on related topics from the blog
Building 100 Micro-Frontends: Lessons from a Solopreneur Journey
How I built and deployed 100 independently deployed micro-frontends on Vercel, the architecture decisions, trade-offs, and what I learned about scaling a one-person dev operation.
AI Integration Patterns for Web Developers: A Practical Guide
Practical patterns for integrating AI into web applications — from prompt engineering and streaming responses to building AI-powered tools that solve real user problems.
Onlook: The Cursor for Designers - AI-Powered Design Tool
Discover Onlook, a free AI tool that helps designers create websites, prototypes, and designs with real-time code generation using Next.js and TailwindCSS.
Related Projects
More in Tech Domain · Book Dev