Site System
The architecture of marklawler.dev: content collections, routing, and maintainability.
This documents how the site works and why.
What I’m optimizing for
- content independence (edit markdown, pages update)
- predictable structure
- minimal custom complexity
- easy deployment
Current state
- Sections and subsections are markdown-driven
- Routing is dynamic
- Cards and navigation share components to prevent drift