What an author's website taught me about structuring a portfolio

The easy version of an author website is one page: photo, book cover, buy link. It works, and it under-serves everyone the moment the book actually launches — the press wants quotes, readers want a first chapter, event attendees need an RSVP, and none of that fits on a single scroll.

The more interesting pattern splits the identity into scoped sub-systems that share one visual language but solve separate jobs: a book microsite, a chapter reader, a press room, an events flow. Each is simple on its own. The complexity is in coordinating five simple systems, not building one complicated one.

That's the model behind this portfolio's own split between /work, /journal, /capabilities and /services. Each answers one question a visitor might have — what has he built, what does he think about, what can he do, what would it cost — rather than trying to answer all four on one page.