Web & architecture
A smaller digital footprint.
The design and implementation of this portfolio: a site that introduces the person, makes room for work, and gives ideas a home with optional consent-based analytics.
Status
Built
Contribution
Design, architecture and implementation of this site.
How much can a personal site do while asking for as little as possible?
- Give the portfolio, profile and journal their own pages, with a consistent visual identity and direct navigation.
- Generate static pages at build time. Keep fonts and assets local, and use public profile links instead of collecting messages.
- Keep private source documents out of the project. Review visible content, metadata and generated files before any publication.
- Decision: deliver static pages rather than run a server for page requests.
- Reason: the current pages do not need accounts, stored messages or server-side processing.
- Cost: a content change requires a new build and deployment. Private source material must stay outside the repository as well as outside the visible pages.
- Revisit when: a reader needs something that cannot be provided with static pages.
Static pages with no visitor account or message database. Optional analytics is controlled separately by visitor consent and the hostname.