Albergo le Terme | Webflow Build for a Tuscan Spa Resort by Raja Zeeshan AliAlbergo le Terme | Webflow Build for a Tuscan Spa Resort by Raja Zeeshan Ali
Albergo le Terme | Webflow Build for a Tuscan Spa Resort
A 15th-century thermal resort in Tuscany, turning a design into a fully responsive Webflow site
The place
Bagno Vignoni is the kind of village you stumble into and don't quite want to leave. A pool of steaming thermal water sits in the middle of the square, has done since the Etruscans. Around it, a 15th-century palace built by Rossellino, once Pope Pius II's summer house.
Today it's Albergo le Terme: a thermal spa resort run by the same family for four generations.
So yeah. The brief carried some weight.
Where I came in
Onlab had designed it beautifully. My job was to make it real in Webflow, hotel, spa, restaurant, B&B, weddings, events, cooking classes, all under one roof, in two languages.
A whole little universe.
The interesting part
Here's the thing about a really good design file, it tells you what the site should look like, but not always how it should behave. The mega menu was the first place I felt that.
Multiple properties, multiple services, two languages, every link pulling weight. There was no spec for how it should open, breathe, collapse, or hold up to future content. That logic had to come from somewhere. So I sat with it for a while and figured it out.
The CMS was the same story. With this much content, rooms, treatments, packages, restaurants, events, the structure mattered more than the styling. If I got it wrong, every future update would feel like surgery.
So I mapped it from scratch. Collections, references, the relationships between them, all designed so that the family running this place or whoever maintains it next, would never need to call anyone to add a new offer.
Then there was responsive. The design didn't just shrink down on mobile, it genuinely shifted. Sections rearranged, hierarchies changed, things that sat side-by-side on desktop suddenly had to find their own rhythm on a phone. That's the kind of thing that looks effortless when it's right and broken when it's not. I spent real time getting it right.
The build
Three months, end of 2025 to February 2026. No missed milestones, no panic, no all-nighters. Just steady, careful work, the way this kind of project deserves to be done.
What ended up on the staging server:
2 languages, fully wired into the CMS
25+ custom collections, all talking to each other
4 distinct properties living in one tidy backend
98+ Lighthouse target, built in from day one, not patched on at the end
Zero "what does this padding do?" moments, because the build matched the design
Almost live
The site hasn't launched yet, but it's done. Handed off, sitting quietly, waiting for go.
When it does go live, my hope is the same as it always is: that you can't tell where the design stopped and the build began.
That's the whole job, really.
Could yours be the next one I write about?
If you're building something or have a design that needs to become a real, working site, I'd genuinely love to hear about it.
No proposals, no sales talk, no awkward follow-ups.
Just a 30-minute conversation to see if we'd work well together.
That's how every good project I've ever done has started.