Guide
Posts
Share updates, ask questions, discuss
Posts: Your Progress Trail
Posts are where members share what they are building, ask for feedback, reply to other builders, and keep a visible record of progress. A useful post gives readers enough context to understand the work and one clear reason to respond.
Post when there's something to respond to: product decisions, launch plans, lessons learned, screenshots, or a question you want answered.
Post types
Choose the post type that best matches the reason you are posting. Types help people scan the feed and find the kind of conversation they want to join.
Discussion
For open conversation and anything worth talking about.
What are you trying to figure out? A specific question gets better answers than a broad topic.
What constraints shape the answer: your budget, your timeline, whether you're solo, the stage you're at?
What would a good reply give you: an opinion, an example, someone's war story?
Idea
For early thinking you want reactions to.
What's the idea, and what sparked it? An observation or a frustration is a fine starting point.
How might it play out in practice? Even a rough shape gives people something to react to.
Where does it fall apart? Name the weak spot yourself and people will stress-test it with you instead of politely nodding.
Milestone
For progress that took real work to reach.
What's live now that wasn't before? Numbers, screenshots, and links beat adjectives.
What did it take to get there? The detours usually teach more than the result.
What's next, and do you want anyone holding you to it? A next step said in public is harder to quietly drop.
Support
For when you're stuck and need some help.
Where exactly are you stuck? Vague problems get vague advice, so name the page, the metric, or the decision.
What have you tried and what happened? Save people from suggesting things you've already ruled out.
What does useful help look like: blunt feedback, an intro, someone who's been through this exact thing?
One post, many places
By default, your post goes out to the timeline, the main feed where members catch up on what's happening across Commune. It also lands on your profile, building a public record of what you're working on and how you think. If the update is about something you're building, attach it to your project so anyone following the product can track its progress in one place.
Where you post also shapes who sees it. Groups suit conversations that belong to a specific community or private space. Topics work like open boards for broader subject areas that members browse and follow, and a post can sit in one topic, or several at once on a paid membership. Inside the text itself, hashtags add lightweight labels: use them to connect recurring themes or make a specific term easier to find.
How posts are scored
Every post and reply earns a flat 5 Gold and 5 XP the moment you publish. That baseline rewards showing up — the act of contributing counts before anyone has read a word, so there's never a reason not to start.
Everything above that baseline is earned. After you post, an AI evaluator reads top-level posts and scores them for signal, relevance, and usefulness: does this give other builders something real to engage with? The stronger the score, the larger the bonus stacked on top of the base reward.
Decent
+3
Good
+6
Great
+10
Exceptional
+15
The ceiling is deliberately high. A post that lands in the 90s earns five times the bonus of one that scrapes into the 60s, because the posts that teach something, show evidence, or open a real question are the ones worth pulling to the top of the feed.
Replies are held to a lighter standard. A quick thanks, a note of agreement, a bit of encouragement, or a follow-up question is real conversation, and the evaluator treats it that way instead of demanding every reply carry a full argument.
The same system runs in reverse. Gibberish, spam, unrelated promotion, and abuse don't just miss the bonus — they can pull rewards back down. The cheapest way to farm Gold is also the fastest way to lose it.
How our AI evaluates and scores posts
Want to land in the higher tiers? Four things move the score more than anything else.
Specific context
Name the project, decision, user problem, experiment, or launch stage so people know what they are responding to.
Useful detail
Include what changed, what you tried, what failed, what surprised you, or what tradeoff you are weighing.
Evidence when available
Screenshots, links, numbers, examples, or before-and-after notes make a post easier to judge and help.
A clear next step
Say whether you want critique, testing, ideas, encouragement, examples, or a decision between options.
Scores aren't the whole picture. Replies, likes, bookmarks, awards, and views all feed discovery, so posts that start real conversations travel further. The reliable way to reach more builders is to write for the ones you want to hear from, make the context clear, and give them a concrete way to help.