Where [Ideal Client] come together to [Transformation], with [what the community offers]
Same design system as every page, different composition. A community page leads with belonging, so the H1 is an invitation, not a problem statement. That's why this page looks unlike the service page — the blocks differ, the design doesn't.
Keyword sits in the community name. One always, two max.
Ways-to-join tiers, events and the resource library are library blocks — off by default, switched on only when the client has real content for them. Shown lean here: hero, what you get, proof, join, FAQ, close.
Replaces the homepage's problem/solution. A community page shows what belonging gives, not a problem it fixes.
An in-page block, not a separate page — the nav dropdown jumps here. Preview enough to show the value, gate enough to be a reason to join: access requires the join, which is what feeds the nurture sequence. Built only when the client has a real library. Promotion rule: any of these blocks earns its own page only when the keyword research’s Situation Verdicts show real decision-stage demand for it — in-page by default, promoted by evidence.
Every guide is a lead magnet: the download asks for an email and must name the nurture sequence it enters — no orphan captures. Built only when guides exist; the nav dropdown jumps here.
Hides entirely when nothing is scheduled — an empty events list reads as a dead community. Event schema per event with venue and date. Booking can link out to the client’s ticketing where one exists.
On the homepage the capture is an early strip. On a community page it's the centre of the page — placed straight after the benefits, so the ask lands while the value is still on screen. Everything below it (resources, guides, events) is depth for the not-yet-convinced.
The free community has no “members” — joining is free and always will be, so the copy says you, the community, everyone inside — never member or membership. Those words belong to the paid Membership page, where they are accurate. If the client has their own word for their people, the questionnaire captures it and Brandi uses it.
The Brandi platform’s CRM capture form, styled to the design system — name, email and at most one welcoming question. Every join is tagged as part of the community and enters the welcome sequence. Never a bare email field to nowhere, never a mailto.
Fallback "Questions, answered" on pages with no single action.
Meets them at the hesitation point, right after the offer. If the client gives an FAQ link, their real questions are the source of truth and Brandi only fills gaps; with no link, Brandi generates from pain points and offer terms. On secondary pages the questions are the real ones people searched for that page's keyword. Include a risk reversal — a guarantee, a free first step, a no-obligation call.
Every form on the site — the newsletter here, every magnet download, the contact form, the community join — is the Brandi platform’s CRM capture form, embedded and styled to the design system. Every submission lands in the CRM tagged with its source and enters its named sequence. Never a mailto link, never a third-party form.
Consistent name, address and phone across the web is what local search scores. When a brand won't publish a street address, the footer carries city or region only, and the full details live on the Contact page with local business schema and a Google Business Profile. The signal is kept; the street address is not forced into the footer.
In care, health or youth sectors, a care or crisis resource in the footer is required, not optional.