Case study
Devsan Wiki
A public Quartz-powered digital garden — daily notes, topic maps, evergreen learning.
Summary
A living wiki where I write what I learn and build. Quartz 4 over iCloud-synced Obsidian, with a three-layer model: daily logs feed topic maps which graduate to evergreen notes. Public at the Devsan-wiki repo.
Problem
Engineers learn fast and forget faster. The real cost isn't learning — it's losing the thing the day after. I wanted a system that captured what I learn and built, and then turned it into something I can reuse, share, and link to without ceremony.
Approach
I picked Obsidian for capture and Quartz for publish — the former because daily-log friction is the lowest, the latter because it's static, fast, and renders graph + backlinks well. iCloud syncs between Mac and phone; a GitHub action publishes Quartz on push. The operating model is three layers. Daily logs are wherever I'm working and don't ask permission. Topic maps (AI agents, IoT, programming, business) act as hubs that pull notes together. Evergreen notes are the polished form — only promoted after I've used them at least twice. The system avoids the mistake of trying to organize everything upfront; it lets structure emerge.
Architecture
Result
A public garden that's still growing — 80+ notes, daily writing rhythm, topic maps that visibly densify week over week. It doubles as my own search engine and as the source of truth for the chatbot on this site.
Highlights
- 80+ public notes across IoT, AI agents, programming, and product
- Three-layer operating model — daily logs → topic maps → evergreen notes
- Synced via iCloud and git so capture happens wherever I am
Have something similar?