Most people building a community start with a button. They pick a platform, turn on sign-ups, and share the link. Then they wonder why new members drift in, look around, and quietly leave. The button was never the problem. The problem is that a community needs a small set of pages doing specific jobs, and a lone sign-up link does none of them well.
This guide maps the durable structure a community site needs: a public hub that explains the place, a join flow that turns interest into membership, and a member home that helps people land and stay. These three areas show up whether you run your community on a forum, a chat app, a course platform, or your own site. The features change constantly. The structure does not. If you are still deciding what "owned audience" even means and why it matters, the community-building foundations are a good companion read, and this post fits inside the broader move from rented to owned audience.
The Three Jobs a Community Site Does: Attract, Convert, and Retain
Before you think about pages, think about jobs. Every community website is really doing three things, in sequence, for three different people.
- Attract is for a stranger. They have heard about you, or stumbled in, and they need to understand what this is and whether it is for them.
- Convert is for someone who is interested. They have decided they might want in, and now you need to make joining easy without making it meaningless.
- Retain is for a member. They are already inside, and they need to know what to do, where to go, and why to come back.
Most struggling communities are unbalanced across these three. Some pour everything into attracting and have no plan for what happens after someone joins. Others guard the gates so tightly that no stranger ever gets enough information to want in. Mapping your site to these three jobs keeps you honest about which one you are neglecting.
A useful way to picture it: the public hub does the attracting, the join flow does the converting, and the member home does the retaining. Each section serves one job for one person. When a page tries to do all three at once, it usually does none of them.
The Public Hub: What a Stranger Needs to Understand Before Joining
The public hub is the part of your community a non-member can see. Its only job is to help a stranger decide, quickly, whether this place is for them. That is it. It is not where you teach, deliver value, or run the community itself. It is the front door and the window display.
A stranger arriving cold usually has four questions, and your public hub should answer them without making anyone hunt:
- What is this? A plain-language description of the community and what it is about. Not a mission statement. A sentence a member would actually use to describe it to a friend.
- Who is it for? Specific enough that the right person thinks "that's me" and the wrong person self-selects out. "For early-stage SaaS founders" beats "for entrepreneurs."
- What happens here? What members actually do — discussions, weekly calls, shared resources, feedback, accountability. Concrete activities, not vague promises.
- How do I join? A single obvious next step. One primary action, not five competing buttons.
The public hub is also where your homepage does real work. If your community lives on its own site, the homepage that funnels people in is the highest-traffic version of this front door, and it should point clearly toward joining rather than burying the path under navigation.
What to leave out of the public hub
A common mistake is treating the public hub like a member area. You do not need to show every discussion, every resource, or the full member directory to a stranger. Two reasons. First, it overwhelms someone who is still deciding. Second, it removes any reason to join, because they can see everything already. Show enough to build understanding and a little curiosity. Keep the rest behind the door.
Examples across community types
- A course community might use the public hub to explain that members get peer feedback and weekly office hours alongside the course, so a prospective student understands the community is part of the value, not an afterthought.
- A local-business community — say a neighborhood cafe building a regulars' group — might keep the public hub simple: what the group is, that it shares early access to events and a members' table on Fridays, and how to sign up next time you are in.
- A creator community might use the hub to show the kinds of conversations that happen and the rhythm of the place (a monthly theme, a weekly thread), so a follower can picture themselves participating before they commit.
The Join Flow: Lowering Friction Without Lowering Commitment
The join flow is everything between "I'm interested" and "I'm in and oriented." It is the most underbuilt part of most community sites, usually compressed into a single form and a confirmation page. That gap is where good intentions go to die.
The goal here is a balance that sounds contradictory but is not: reduce friction, keep commitment. You want joining to be easy. You also want people to arrive with a small sense of having chosen this, because effortless joins produce effortless leaves.
Reduce friction where it is pointless
Friction that adds no value just costs you members. Trim it:
- Ask only for what you genuinely need at the start. A name and an email is often enough. You can learn the rest once they are inside.
- Make the very next step obvious. After someone signs up, they should never be staring at a blank screen wondering what just happened.
- Set expectations on the form itself: what they will receive, how often, and what happens next.
Keep commitment where it matters
Commitment is not about adding hoops. It is about giving someone a moment to invest, even slightly, so the membership means something.
- A short intro prompt ("tell us one thing you're working on") does double duty: it warms up the new member and gives existing members something to welcome.
- A clear statement of what the community expects — be kind, no spam, participate — lets people opt in to the norms, not just the access.
- A single first action ("post your introduction in the welcome thread") turns a passive sign-up into a first contribution.
A quick honesty note: none of this manufactures urgency or scarcity, and it should not. Fake countdowns and "only 3 spots left" theatrics erode trust with exactly the people you want. Real commitment comes from clarity about what the place is, not pressure about missing out.
Where the join flow connects to a launch
If you are opening a community for the first time or reopening enrollment, the join flow is the thing your campaign points at. It is worth designing the page and the campaign together so the messaging matches what people find when they arrive. When you are ready, plan the launch that opens the doors so traffic lands on a join flow that is ready for it.
The Member Home: Orientation, Rituals, and Where to Start
The member home is the first thing someone sees after they join and every time they return. Its job is retention, and it does that mainly by reducing confusion. A new member who logs in and does not know where to go will usually not come back. A returning member who cannot find the current conversation drifts away over weeks.
A member home does three things well:
- Orient. Make it obvious where the main activity is, what is happening now, and what a new person should do first. A short "start here" area pays for itself many times over.
- Surface rituals. Communities stay alive on rhythm — the weekly thread, the monthly call, the Friday wins post. The member home should make the current ritual visible so people know when to show up and for what.
- Point to where to start. New members and returning-after-a-break members both need a low-stakes first action. A "introduce yourself" prompt, a current discussion to react to, a single resource to grab.
A simple member-home checklist
Use this as a baseline regardless of platform:
- A short welcome that says where to begin
- The current or upcoming ritual (call, thread, theme) clearly visible
- One obvious low-stakes action for a brand-new member
- A way to find the main, active conversation without searching
- A place to find help or ask a question if confused
Examples across community types
- A course community member home might lead with the current cohort's discussion and the next office-hours time, so students always know the live thing to engage with rather than digging through old material.
- A local-business community member home — for that cafe group — might simply show the next members' event and a "say hi" thread, because the value is mostly in-person and the digital home just keeps the rhythm between visits.
- A creator community member home might foreground this month's theme and the active thread, so a member who has been away for two weeks can re-enter without feeling lost.
Mapping Sections to Community Lifecycle Stage
You do not need all of this on day one, and building it all before you have members is a common way to stall. The right structure depends on where your community is in its life.
| Lifecycle stage | What the site mostly needs | What can wait |
|---|---|---|
| Pre-launch / forming | A clear public hub and a simple join flow | A full member home; rituals are still being figured out |
| Early / small | A working member home with one ritual and a "start here" | Elaborate navigation, member directories, multiple spaces |
| Growing | Stronger orientation, a visible ritual, easy access to the main conversation | Over-segmenting into many sub-spaces too early |
| Established | Clear structure across all three jobs, refined onboarding | Constant redesigns; stability matters more than novelty |
The pattern: in the early stages, lean public-hub and join-flow heavy, because your problem is getting the right people in. As you grow, weight shifts toward the member home, because your problem becomes keeping people oriented and returning. Build the section that matches your current bottleneck, not the one that looks impressive.
Durable Structure vs Platform-Specific Features
This is the distinction that keeps your community site from becoming a rebuild project every year. The three jobs — attract, convert, retain — and the three sections — public hub, join flow, member home — are durable. They describe what a community needs no matter where it lives. Platform features are not durable. They change, get renamed, get removed, and vary from tool to tool.
So separate the two in your own planning. Write down the structure first: "we need a public hub that answers these four questions, a join flow that does X, a member home that surfaces our weekly ritual." Then, and only then, ask which features of your current platform serve each of those jobs.
A few honest cautions, because platform mechanics shift constantly:
- Specific capabilities — what a given forum, chat app, or course platform lets you customize, gate, or automate — change over time and differ by plan. Confirm current behavior against the platform's official documentation rather than assuming a feature still works the way a tutorial described it.
- Anything you read about reach, notifications, or who-sees-what inside a platform is volatile. Do not build your retention plan on a notification behavior that may change.
- If a platform gives you a feature that maps neatly to one of the three jobs, use it. If it does not, the job still needs doing — you may just do it more manually, or on a page you control.
If you want your most durable assets to live somewhere you own rather than rent, the move toward an owned audience is the larger strategy this fits into. You can run the community itself anywhere; the public hub and join flow are good candidates for pages you control, so they survive a platform change.
A quick, important truth: structure helps people find belonging, but it does not create belonging on its own. A perfectly mapped site with no one welcoming new members, no consistent ritual, and no founder showing up will still feel empty. Treat these sections as scaffolding for human connection, not a substitute for it. The pages make it easy for people to do the things that build community. The people still have to do them.
In Plain English
A community website is not one page with a sign-up button. It is three areas doing three jobs: a public hub that helps a stranger understand and decide, a join flow that turns interest into an oriented new member without fake pressure, and a member home that helps people land, find the current rhythm, and come back.
This matters most for founders, coaches, course creators, and small businesses who keep losing new members between "interested" and "active." If that is your gap, the fix is usually not more marketing — it is one of these three sections being missing or unclear.
When to use it: map all three early, but build the one that matches your current bottleneck. Forming a community? Focus on the public hub and join flow. Already have members who go quiet? Build the member home. And keep the structure separate from your platform's features, so a tool change never forces you to rethink what your community fundamentally needs.
What to do next: sketch the three sections for your own community on a single page, then pull the practical pieces together with Owned Audience 101 and the wider Owned Audience hub. If you are still defining the human side of all this, revisit the Community Building hub before you build a single page. Plan your community hub around the jobs first, and the pages will tell you what they need to be.