architektgol
2026A portfolio site for an architecture practice, built with a non-technical client and handed over so they run it themselves.
Problem
The practice had visualisations and completed works but no presence prospective clients could find. Work lived in shared drives and social posts, which search engines never surfaced.
Approach
Most of this job was not the code. It was sitting with the architect, turning "it should look professional" into decisions we could both check, and agreeing what mattered — being findable — before anything was built. Technically: static generation, so every project page ships as pre-rendered HTML that crawlers index directly. The current version replaces the photography with drawn elevations and axonometrics, and carries a project index with a page per project — each one the drawing, the description and the project’s facts, rather than a lightbox of images that says nothing.
Result
The site is indexed and findable in Google, and the practice publishes new work to it without me. That was the point: a handover the client could actually operate, rather than a site that needed me every time it changed.
Walkthrough
