You decided to build a community. Good. The next decision trips up more people than any plugin setting ever will: what shape should it take? A forum? A Q&A board like Stack Overflow? An upvoted ideas list? A fast-scrolling feed where members share their work?
This is not a cosmetic choice. The format you pick decides what behavior your community rewards, what content rises to the top, and whether people come back. A support audience dumped into a chronological feed will drown. A casual hangout forced into a strict question-and-answer format will go quiet. Pick the wrong shape and you will spend months wondering why engagement stalled when the real problem was structural.
Here is the good news. In Jetonomy, format is a property of each space, not of your whole site. You are not choosing one shape for everything. You are matching each shape to a job, and you can run as many shapes as you have jobs. Let’s walk through the four formats, the job each one does best, and how to decide.
Start with the job, not the format
Before you compare features, name the job. Every community format exists to optimize one signal. Get the job right and the format almost picks itself.
There are really only five jobs a community space can do well:
- Discuss an open-ended topic where there is no single right answer.
- Answer a specific question so the solution is findable later.
- Prioritize what to build or change next, by popular demand.
- Showcase work so people can admire, learn from, and react to it.
- Chatter in short, fast, low-stakes updates.
Each of those maps to one of Jetonomy’s four space types, with the last two sharing the Show & Tell feed. Match the job to the format and you stop fighting your own tool.
The four Jetonomy space types
Jetonomy ships four space types in the free plugin. Each one changes how content is created, sorted, and rewarded. They are not skins on the same list. The underlying behavior differs.
Forum: open discussion
A discussion forum is the classic threaded format. Someone starts a topic, other people reply, and the conversation branches as needed. There is no single correct answer and no winner. The forum optimizes for breadth of conversation.
Use a forum when the value is in the back-and-forth itself: introductions, general discussion, debate, off-topic chatter that bonds a community, or any subject where ten good perspectives beat one accepted answer. If your members mostly want to talk to each other rather than extract a fact, a forum is your home base.
Q&A: one accepted answer
A Q&A space looks similar at a glance but behaves differently in the ways that matter. A member asks a question. Others post answers, and members can vote on them. Replies show oldest first by default, with a best option for readers who want the top-voted answers. The question’s author (or a moderator) marks one answer as accepted, and that answer is shown first as the solution.
The signal a Q&A space optimizes is findability of the right answer. That makes it the natural format for product support, technical help, and anything you want to turn into a searchable knowledge base. Over time a good Q&A space becomes a deflection engine: the next person with the same question finds the accepted answer instead of asking again. If you run support today through a ticket queue, a Q&A space is the public, compounding version of that work.
Ideas board and roadmap: upvoted requests
An ideas board flips the direction of value. Instead of members asking you for help, they tell you what to build. Anyone can post an idea, and everyone can upvote. The most-wanted ideas rise to the top, so you get a live, demand-weighted view of what your audience actually wants.
The roadmap is the other half. You move each idea through status badges (planned, in progress, shipped, and so on) so members can see where their request stands without emailing you. The upvotes tell you what to build; the badges tell members that you are listening. Together they replace the black hole that most feedback inboxes become. The signal here is prioritization by genuine demand.
Show & Tell: a short-form feed
The fourth type is listed as Feed in the admin, and it is the home for Show & Tell. Posts render inline as a short-form feed, so members can share what they made, a quick update, or a link worth passing on without writing an essay, and others can scroll through without opening each thread. Think finished projects, setups, member wins, or a thought of the day.
The signal it optimizes is momentum and recognition. It keeps a community feeling alive between the longer-form posts elsewhere, and it gives members a place to show their work and feel proud to belong. It is a poor place to store knowledge, because a feed rewards what is fresh, so keep reference answers in a Q&A space.
The decision table
Here is the whole framework in one place. Find your primary job in the middle column, and the format on the left is your answer.
| Format | Best for | The signal it optimizes |
|---|---|---|
| Forum | Open discussion, introductions, debate, community bonding | Breadth of conversation |
| Q&A | Product support, technical help, building a knowledge base | Findability of the right answer |
| Ideas board and roadmap | Feature requests, feedback, deciding what to build next | Prioritization by genuine demand |
| Show & Tell (Feed) | Member work, status updates, quick links, daily rhythm | Momentum and recognition |
If two rows feel right, that is not a tie you need to break. It is a sign you have two jobs, which brings us to the most important point in this guide.
The real answer is usually more than one
Almost every healthy community does several jobs at once. Your members want to ask support questions and request features and show off what they built and hang out. Forcing all of that into a single format is exactly how communities stall: the support seekers drown out the showcasers, the feature requests get buried in general chatter, and nobody can find anything a week later.
Jetonomy is built so you do not have to compromise. Because the format lives on each space, you can run a discussion forum, a Q&A knowledge base, an ideas board with a roadmap, and a Show & Tell feed at the same time, from one plugin, on one self-hosted WordPress site. There is no separate product to buy for each shape and no integration to wire up between them. They share the same members, the same trust levels, the same moderation, and the same custom jt_* database tables underneath.
A common starting layout looks like this:
- A forum space called General for discussion and introductions.
- A Q&A space called Help that doubles as your support knowledge base.
- An ideas board called Feature Requests wired to a public roadmap.
- A Show & Tell feed for member work and quick updates between the bigger posts.
You do not need all four on day one. Start with the one format that matches your single most important job, prove it works, and add spaces as new jobs appear. The point is that the ceiling is not “pick one.” The ceiling is “run exactly the shapes your community needs.”
This is also the difference between a community platform and a single-purpose tool. A standalone forum script can only ever be a forum. A standalone Q&A app can only ever do Q&A. When your audience inevitably wants the other jobs done too, you are stuck bolting on a second product. Choosing a platform that does all four from the start is the long-term decision. If you are weighing the broader build, our guide on how to build a community on WordPress covers the full picture.
What each format asks of you each week
A format is also a commitment of your time, so choose with that in mind. A forum needs a host: someone who greets newcomers and keeps conversations civil. A Q&A space needs someone to watch for unanswered questions, because a question with no reply is the worst advert for the space.
An ideas board needs a weekly review. Members vote, but only a moderator can set an idea’s status, and the author is notified when you do. If nobody changes statuses, the board looks abandoned within a month. A Show & Tell feed needs the least upkeep, though it benefits from you posting first and reacting early.
Each space can also be tuned on its own. You can choose who may post, who may reply, whether voting is on, and whether new posts wait for approval. A support space can be open to everyone while a feature board is held for review.
Rules that stay true across all four formats
Some behaviours are the same everywhere, and it is easier to learn them once. Accepting an answer is a Q&A feature only. Forum, Ideas and Show & Tell spaces never show an accepted-answer marker, so do not promise members one outside a Q&A space.
Trust levels work the same in every format. New accounts start with tighter daily limits, and levels one to three are earned from activity. They set a ceiling on what a member may do, and they never hand out moderator powers. Moderators come from the roles you assign.
Voting is also shared. Members can vote on posts, and reputation rises with upvotes and with accepted answers, so a helpful Q&A contributor and a popular idea author both climb the leaderboard.
Three layouts we see working
A software product. One Q&A space for help, one Ideas board for requests, and a forum for general talk. Our support forum journey and ideas board journey walk through the first two in detail.
A course business. A Q&A space per course, gated to enrolled students, plus a Show & Tell space for finished work. The Q&A peer-learning journey covers the first, and the Show & Tell journey covers the second.
A paid membership. A forum for discussion, a feed for daily updates, and gated access through your membership plugin. The monetization guide explains the gate.
What the formats do not cover
None of the four formats is a chat room. Jetonomy has no live chat, voice or video, and no built-in Discord or Slack bridge. If your community lives on real-time conversation, plan to keep a chat tool beside it.
A space’s type can be changed from its edit screen, but that is not a casual switch on a busy space. Features such as accepted answers only apply in Q&A spaces, so rehearse the change on a copy of the site first.
Where the rest of the family fits
Jetonomy is the discussion layer. BuddyNext is a separate plugin from the same team that adds profiles, an activity feed and groups. With both active, the forum adopts BuddyNext’s look and BuddyNext owns the page header and navigation. See the BuddyNext partner page.
Learnomy, the course plugin, can gate a space with Jetonomy Pro, so enrolled students enter the right Q&A space automatically. The Learnomy partner page has the detail. Other pieces from the same team, such as WP Career Board, Listora and Eventonomy, run beside Jetonomy on the same site as separate plugins.
How to set this up in Jetonomy
Setting the format is a per-space choice, and it is part of the free plugin. There is nothing to unlock.
- Install and activate Jetonomy on your WordPress site. It is free and self-hosted, so your community and its data live on your own server in your own database.
- Create a new space. During creation you choose the space type: Forum, Q&A, Ideas, or Feed (Show & Tell).
- Name the space for its job. Help for Q&A, Feature Requests for Ideas, Showcase for Show & Tell, and so on. Clear names tell members what each space is for before they post.
- Repeat for each job you identified. Add a second and third space in whatever formats fit. They all share members, trust levels, and moderation automatically.
- If you are migrating from another platform, the one-click importers can bring your existing content across so you start populated rather than empty.
That is the whole setup. Format is a setting on the space, not a fork in the road for your entire site, which means you are free to experiment. Spin up a Q&A space, see if your audience uses it, and add a Show & Tell next month if the work starts piling up.
When you outgrow the basics, Jetonomy Pro (from 69 dollars per year) layers on the extras that larger communities want, but every one of the four space types is in the free plugin. You can build a genuinely multi-format community without spending anything.
Pick the job first. Let the job pick the format. And remember that “which one” is usually the wrong question. The right one is “which ones.” Browse the full feature set to see how the pieces fit together.