
Your schedule lives on your site. Your courses live on your site. The people who gather around your teaching are not a smaller thing than either — so when the community conversation happens on a rented platform, the warmest part of your studio is the one part you don't hold. Gather Grove Communities puts the room where everything else already is: inside your WordPress site, in your database, under your name. Here's what it actually gives a studio, what's free, and what it costs.
Everything is built on spaces — named rooms with their own roster, posts, and moderation. Not one infinite feed with an algorithm deciding what surfaces; rooms, the way a studio actually works. A welcome room. An announcements room. A room for the Tuesday cohort.
Each room chooses its shape. Open conversation, or moderators-only broadcast — which is exactly what an announcements room wants to be. Members still comment and react in a broadcast room; it's "we speak, you respond," not a velvet rope.
Every space is private by default. Keep it private and outsiders get an ordinary 404 — never a "this room is private" hint that it exists at all, which is the small difference between discretion and a locked door with a sign on it. You can also flip a room to public-read, so it gets a calm, indexable page: good for a welcome room that doubles as a front porch. (Public rooms are a Pro feature — see the tiers below.)
A room is two columns on a wide screen, one on a phone. The conversation runs down the middle. Alongside it sits the rail, which exists to orient you:
Those shelves are worth their own paragraph. Materials holds handouts, worksheets and recordings — anything with a file. Links holds readings and references. The room's instructors and moderators fill them from inside the room: upload the handout right there, drop the reading link, put them in the order you want them read. No leaving for wp-admin and no knowing which screen to find, which is exactly why, in practice, shelves used to stay empty. (Shelves are Pro.)
Separately, pinned posts sit as cards across the top, above the conversation. One pin riding the top of a feed is fine; five push the live conversation permanently below the fold and the room reads as abandoned. As cards, the pins stay visible and the conversation still starts right underneath.
A few smaller things that add up to a room feeling looked-after:
An invitation is how someone joins: you name them, tick the rooms they belong in, and they click one link and they're in — account created, rooms joined, signed in, no password to invent. The invitation also says what they're arriving as: member, instructor, or moderator, so a facilitator lands already marked as one instead of being promoted by hand afterwards.
There is deliberately no public "sign up" door. Every member is someone you let in. For a studio that is a feature, not a limitation — your community is your students, not the internet.
Most live chat accumulates: channels that scroll forever, unread counts that become guilt. A campfire is the opposite. You light it for a moment — launch night, office hours, the after-class hang — a banner announces it while it burns, people step in and talk in real time, and when it's over, it's gone.
Deliberately gone. That's not a missing feature, it's the feature. A campfire is a moment, not a record, and everyone in it can feel the difference: presence is light and nobody is performing for the archive. The parts worth keeping, the host pins — and after the fire is doused, one button writes those pinned moments into a keepsake post in a permanent room, each voice quoted and credited. The evening ends; the best of it stays where the community lives.
You light one from inside the room it belongs to, which turns out to be the natural way — that room is both the guest list and the fire's home, it carries the live banner while the fire burns, and the keepsake is offered back to it first. Hosts get warm tools rather than heavy ones: last call, slow mode, pinning, and a two-tap douse. Who may light one is a dial from closed to open — admins only, also your instructors, or any member — and widening it changes who can start a fire, never who can be gathered into one. (Campfires are Pro.)
A post can be more than prose. Rooms can be given announcements — posts that stand out, and that still reach members who've asked to hear about highlights only — and proposals, for things a group is deciding together. Members add their backing with one click, and the board orders by how much support each has gathered.
Here's the line I care about, and it's permanent: support sits on the proposal, never on the person who wrote it. There is no score attached to any member, no ranking of people, no running total of anyone's contributions anywhere in Gather Grove. Communities ranks ideas, because a group deciding something needs to see which idea has weight. It does not rank people, because a room where members can be ordered best-to-worst stops being a room.
Announcements are a moderator's to write; proposals are anyone's — a request board only staff can file into is a suggestion box with the lid welded shut. Both are off in every room until you switch them on, and a room that hasn't asked for them shows no chooser at all.
A member's profile publishes field by field, with consent per field. Name, photo, bio, pronouns, location — each one is shared because the member chose to share it, and the choice sits right next to the field, at the moment it matters. The member directory is doubly opt-in: the studio turns it on, and each member individually chooses to appear. A public room never overrides anyone's settings — an author who hasn't published their profile simply appears as "a member."
This is what consent looks like when it's a design principle instead of a settings page you find later.
This is the part a standalone community platform structurally cannot do, because it doesn't know anything about your classes.
Nobody has to remember to create the room. The class already knows who's in it.
The free tier is a genuinely useful members-only community, not a paywall teaser — and it's worth being exact about the line, because the split isn't where people usually guess.
The principle behind that line: free is the community itself — spaces, posts, profiles, the feed — because that's what members feel. Pro is everything that leans on the sibling plugins or grows the studio: the automated lifecycles, the messaging, the public surface.
And gating is behavioral, never destructive. The cleanup pathways — lobby archiving, cohort graduation — are deliberately not gated, so a lapsed plan never strands live data. Your rooms don't hold your members hostage on your behalf.
The community on gathergrove.io runs on this exact plugin, and everything above was built by running it: the rail exists because a room with no rail felt like shouting into a void; the shelves are curated from inside the room because, from wp-admin, they never got curated at all; links auto-embed because the field nobody used was the field I'd built.
That's the standard I want to be held to. If a room misbehaves, it misbehaves in my house first.
Communities is shipping — it passed 1.0 and is at 1.0.13 as I write this, moving in the open. See the plugins page for where it sits in the suite, the docs for every detail including the honest free-vs-pro split, and the roadmap for what's next.
Or just step into ours. It's early in there, which is the good part — the people who pull up a chair first are the ones who shape what it becomes.
Gather Grove Communities is part of the Gather Grove suite — self-hosted, WordPress-native, your data in your database. Your craft. Your people. Your Grove.