Why it exists
The web is better when the canonical version of a person’s work lives somewhere they own. This project starts with a static, file-backed site because the simplest publishing path is usually the one that gets used.
My role
Product direction, information architecture, writing system, visual design, and implementation. The work is deliberately end-to-end because the publishing experience and the public interface need to evolve together.
Decisions
- Content remains in portable Markdown files.
- The “corkboard” is treated as a discovery model, not a literal surface.
- Notes, Essays, and Logs share metadata but may develop different reading behavior.
- Dark mode uses the same semantic tokens instead of becoming a separate design.
- Drafts are safe by default; publishing must be intentional.
Current direction
Replace demonstration content with real residue from active work. The design should become less pristine as screenshots, decisions, failures, and unfinished questions arrive.
History
- August 2026 — First usable slice. Astro collections, primary routes, RSS, and content scaffolding.
- August 2026 — Editorial rebuild. Removed the literal cork treatment and introduced the working-index layout.
- August 2026 — Inhabitation pass. Added content-specific reading modes, project history, wandering paths, and publishing checks.
Outcome so far
The system is ready to hold real material. Its success is no longer a build question; it depends on whether publishing here becomes a habit.