The Marlowe Farm

The Marlowe Farm is a wedding-venue website design concept. The brief: what would a custom-coded site look like for a serious family-run venue — a working Wisconsin farm that hosts six weddings a year — built static-first today and architected to drop into WordPress tomorrow without redesigning a single section?

The wedding-venue category online is dominated by template sites that all collapse into the same shape: a script-font logo, a hero photo of a couple silhouetted against a sunset, a “happily ever after” tagline, a grid of “what’s included” cards (chiavari chairs! market lights! a barrel for a sweetheart-table backdrop!), and a pricing page hidden behind a contact form. The brief was to reject all of that.

The design lead-out:

• An editorial wordmark — “The Marlowe Farm” in Fraunces, with the article and noun as small caps bracketing the display name — instead of the usual script-font monogram.
• A full-bleed property hero with the venue’s barn interior at last light, an italic emphasis on the secondary headline line (“The rest of the time, a farm.”), and a single inquire CTA.
• A “From the editor” pull-quote band between the hero and the first chapter, attributed to the fourth-generation owner. The opening voice is the owner’s, not the marketing copy’s.
• Three editorial chapters — The Property, The Day, Practicalities — in place of the typical service-grid + gallery + FAQ structure. Each chapter has an overline (Chapter I, Chapter II, Chapter III) and a lede that sets the chapter’s premise before any photos or details.
• A day-of timeline rendered as three numbered moments (Morning in the milk house, Ceremony in the field, Dinner in the barn), each a flipped two-column row with photo, time overline, title, and a short descriptive paragraph. Not a checklist.
• A “Practicalities” spec list that surfaces what most venue sites bury: capacity (140 seated), season (May to October), what’s included (the full property for 26 hours, onsite caretaker, parking for 80), and what’s not included (catering, bar, florals, music) — honest detail instead of a “request a quote” wall.
• A three-column Inquire section that lists telephone, email, and in-person tour address. No contact form. The owner’s first name is on the phone line. The address has hours.

The piece is built static for the concept host, but the section architecture maps cleanly onto MetaBox structured fields. A WordPress conversion would slot the hero, editor’s note, chapters, day-of moments, practicalities spec, and inquire section into the same CPTs and field groups already powering this site. No second redesign required.

This is the kind of venue website I would ship for a real family-run wedding farm. Built static-first so it lands a Lighthouse score the templated wedding-marketing platforms cannot match, and architected to convert to WordPress the day the venue wants editor-side control of vendor lists, FAQ, and seasonal pricing notes.