Lawfty D2C

Lawfty.com is the direct-to-consumer side of the business. Someone searching for a lawyer lands here, not on a campaign page for a partner firm. It runs on the same Sanity and Next.js setup as the firm sites, with its own dataset and its own design language.

Pages in the Studio

Content lives in a Pages collection. An editor writes a title, stacks the modules they need, and the slug is generated per locale. Everything goes through a draft and published state, so a page can be worked on and previewed without touching what's live.

The site is bilingual. English and Spanish live in the same document, each with its own slug, so the Español switch in the navigation is a language toggle on one page and not a second site to keep in sync.

Beyond free-form pages, the site is modelled around what the business actually publishes: attorneys, practice areas, locations and their landing pages, blog posts, FAQs and legal pages. Each has its own route. Adding an attorney means filling in a document, and the profile page appears. Redirects and vanity URLs are managed in the CMS too, plus an SEO fallback so a page missing its own metadata still ships with something sensible.

Blocks that repeat across pages are handled by a shared content type. An editor writes one once and reuses it everywhere, and the Studio offers a preset per module type, so you start from a real module and not an empty object.

Type scale

Typography is a set of tokens, so H1 through H6, subtitle, body, disclaimer and caption all come off one scale. An editor picks a level and it looks the same wherever that module ends up. This is the test page I used to check the whole scale in one view.

Navigation

Navigation is driven from the CMS too, including the Practice Areas dropdown. Adding a practice area is a content change, not a deploy.

Legal pages

The legal pages are long and change often, so the table of contents builds itself from the headings in the document instead of being maintained by hand. The last updated date comes from the CMS as well.

Forms and delivery

The contact and attorney enquiry forms post to route handlers on our side, so Zod validates the same shape on the client and the server, and every submission is logged before it leaves the app.

D2C shares a monorepo with the firm sites. The Apollo client, the Redis cache layer, middleware, logging and env handling all come from one shared workspace, so a fix in either app benefits both. Sanity responses are cached in Redis and cleared through an authenticated refresh endpoint when content is published, with New Relic on the browser and server side.

More to come.

---

View website | View Lawfty CMS case study | Contact Me