Verdant Landscapes.
A bespoke, content-rich website for a high-end landscape architecture firm.
A brand this considered deserved a site that matched it.
Verdant Landscapes needed a high-end web presence that mirrored their bespoke, structural approach to landscape architecture. Their existing site was built on an aging page builder — it was slow, wasn't fully responsive, and had no real SEO foundation, so their portfolio of estate and civic work was effectively invisible to search.
The studio's team also had no way to update project pages themselves. Every new commission meant a support ticket and a wait, which meant their most recent work was rarely reflected on the site clients actually saw.
Built for editorial content, and for speed.
I built a bespoke, content-rich marketing site using Next.js and Tailwind CSS, integrated with Sanity CMS so the studio's team can publish new projects, photography, and journal entries themselves — no developer required.
Every image was optimized and served responsively, and the site was rendered server-side for near-instant first paint. Structured metadata and a proper information architecture were built in from the start, rather than bolted on after launch.
What changed after launch.
A perfect performance score, even with full-bleed, high-resolution project photography on every page.
Growth within the first 60 days of launch, driven by the new SEO foundation and faster load times.
New design inquiries generated in that same 60-day window, directly attributable to organic search.
Beyond the numbers, the studio's team now publishes new project pages themselves the same week a commission wraps — the site finally moves at the pace of the work it's showcasing.
Pages are server-rendered with Next.js for near-instant first paint, with every project image served through an optimized, responsive pipeline rather than a single fixed-size export.
Sanity CMS gives the studio's team a structured, editor-friendly way to publish new projects and journal entries without touching code — the content model was designed around how they actually organize their portfolio, not a generic blog schema.
