Deeve Technologies
Client workLanding PagesLovable

Hollow Creek Farmstead

Rustic ecommerce landing page for a full-ecosystem family farm selling fresh produce, pasture-raised meats, and farm supplies. Warm earthy design with CSA subscriptions, product showcases, and a conversion-focused layout rooted in authentic...

ClientDemo for clients
RoleWeb Designer & Front-End Developer
Year2026
TypeLanding Pages, Lovable
Updated24 Sep 2026
Screenshot 2026 04 18 113139
Screenshot 2026-04-18 113139
Overview

A working farm website that feels like a working farm, built as a concept project.

React and TypeScript on Lovable, structured around three distinct buyer paths from the first screen.

Built with
Framer MotionLovableReactTailwind CSSTypeScript
The problem

What was in the way

Farm businesses serve very different buyers from one site, and the buyers want opposite things.

A home cook wants fresh produce, eggs and meat, delivered or collected, this week. A homesteader wants supplies, feed, tools and advice, and is planning a season rather than a meal. A wholesale buyer wants volume and consistency.

Send all of them down the same path and it serves none of them. The home cook wades through feed pricing. The homesteader reads a recipe blog. Both leave.

The usual response is a mega menu, which moves the problem rather than solving it. The visitor still has to work out which of eleven links is for them, on a phone, in a category where nobody is patient.

What I built

Four parts, each with a reason

Three buyer paths, separated on the first screen

Fresh produce, pasture-raised meat and eggs, and farm supplies. Split immediately rather than after a shared introduction.

The decision is made once, at the top, by the visitor rather than by a navigation structure. Everything below is scoped to the path they chose.

Conversion appropriate to each path

Each path resolves to its own action rather than a shared contact form.

Produce resolves to an order or a collection slot. Supplies resolves to a catalogue enquiry. Wholesale resolves to a conversation. A single generic form would force three different intentions into one inbox with no way to tell them apart.

Tone that matches the product

A farm site that looks like a design agency made it actively undermines what is being sold.

The whole proposition is that this is a real farm run by real people. Over-designing it reads as a marketing front for a distributor, which is precisely the suspicion a direct-from-farm business has to overcome.

That is a genuine constraint, not an excuse for a worse site. It means restraint in the motion, honest photography, and typography that reads as considered rather than styled.

A note on this one

This is a concept project, not client work. There is no real farm, no real orders and no results to report.

It exists to demonstrate multi-audience information architecture: how to serve three buyers with different intents from one site without a mega menu and without three separate sites. That problem is common well beyond farming, and it is the part worth looking at here.

How it was built

The engineering underneath

ReactTypeScript, Tailwind CSS and Framer Motion, built on Lovable
Three pathsOne entry point, with the shared layer genuinely shared and each path owning its own call to action
RestrainedMotion used sparingly, because in a category selling authenticity heavy animation is a tell

React with TypeScript, Tailwind CSS and Framer Motion, built on Lovable.

The architecture question here is routing rather than styling. Three paths from one entry point means the shared layer has to stay genuinely shared, and each path has to own its own content and its own call to action, without duplicating the header, the trust signals and the farm story three times.

Motion is used sparingly and deliberately. In a category selling authenticity, heavy animation is a tell.

Framer MotionLovableReactTailwind CSSTypeScript
More work

Projects like this

All projects
Why it matters for your project

I build software, and I measure whether it works.

The same questions I research are the ones I ask on client builds: is it reliable, is it fast, is it easy to use, and is it secure. Those four drove satisfaction in my ICT portal study, and they shape how I scope and test every project.