Wiki
Keep technical notes as tagged, navigable pages instead of loose markdown files.
Technical notes kept as markdown files in repos had no navigation or index.
A public deployment is available to try.
Case Study
Before
Markdown notes in repos are hard to browse: there is no index, sections or tags.
After
Lets a reader browse three technical pages by section and tag and read them in a consistent layout.
How it's solved
Built a static wiki that renders MDX pages with category, tags and last-updated date, through an index page and detail pages.
Trade-offs
Read-only and edited as files in the repo; no in-app or community editing, full-text search, or backlinks.
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
Book Reviews
Book review archive with ratings, categories and key takeaways
Notes App
Single-browser notes: create, edit, search and delete plain-text notes
Translation
Tiny EN/TH word-lookup demo with direction swap
Tech Blog
Technical articles and tutorials