The Community Handbook: A Guide to Great a Community
Welcome! This forum is a shared digital commons. Much like a public park, its beauty and utility depend on how we treat it and each other. This handbook outlines how we interact, disagree, and grow together.
Section 1: The Foundation of Civil Discourse
Our goal is to foster a "high-signal" environment where knowledge is easily found and shared.1.1. Lead with Value
Before posting, ask: Does this move the conversation forward? * Search First: Check if your question has been answered. Contributing to an existing thread is better than starting a duplicate.- Quality over Volume: Avoid "empty" replies like "+1" or "Agreed." Use the Like button to show support without cluttering the feed.
1.2. The "Steel-Man" Principle
When disagreeing, try to understand the other person’s argument so well that you could argue it for them.- Attack Ideas, Not People: Avoid ad hominem attacks or labeling users.
- Respond to Content: Ignore the "tone" and focus on the facts. If a post feels rude, assume positive intent—text often hides nuance.
Section 2: Elite Collaboration Techniques
Moving beyond "being nice" into being an effective contributor.2.1. Precision in Formatting
Structure your posts so they are readable at a glance.- Use the Toolkit: Use bolding for emphasis, code blocks for technical data, and bullet points for lists.
- Descriptive Titles: Use specific titles (e.g., "How to fix JSON export errors") instead of vague ones ("Help please!").
2.2. Context & Citations
Don't assume everyone shares your background knowledge.- Define Jargon: Briefly explain industry-specific terms for newcomers.
- Cite Sources: If you state a fact or statistic, provide a link. It builds your credibility and saves others time.
2.3. The "Edit, Don't Multi-Post" Rule
If you have an afterthought, use the Edit (Pencil) icon on your original post. This prevents unnecessary notifications and keeps the thread history clean.
Section 3: Protecting the Commons
Safety and tidiness are everyone's responsibility.3.1. The "Don't Feed the Troll" Rule
If you encounter "bad" behavior (spam, harassment, or rudeness), do not reply. * Report It: Use the Report tool to alert moderators. Replying validates the behavior; flagging solves it.3.2. Intellectual Property & Privacy
- Own Your Content: Only post material you created or have permission to share.
- Respect Privacy: Never share the private information (doxxing) of others.
- The Front Page Test: If you wouldn't want your post read by a future employer, don't post it.
Section 4: Advanced "Pro" Tips
4.1. The "Closed-Loop" Rule
If you ask for help and find the answer elsewhere, come back and post it. * The "Future You" Test: Imagine someone finding your thread in 2 years. Does it end with "Fixed it!" (frustrating) or "Fixed it by doing X, Y, and Z" (heroic)?4.2. Be the "Janitor" (Gently)
You don’t need to be a moderator to help.- Friendly Redirects: If you see a post in the wrong category, say: "Hey! This is a great question, but it might get more eyes in the #TechSupport channel." * Tagging Experts: If you know someone who has the answer, tag them (e.g., @JaneDoe) to bridge the gap.
4.3. No "Vampire" Posting
Avoid "sucking the energy" out of the room by demanding immediate help without providing details.- Show Your Work: Instead of saying "It doesn't work," say "I tried X and Y, and I expected Z, but I got Error 404."
- Respect Time: People are helping for free. Make it as easy as possible for them to help you.
4.4. The "Bump" Limit
If nobody replies to your post, don't keep typing "Anyone?" every hour.- Wait 24 Hours: Give the community time to see it.
- Add Context: If you must "bump" a post, add a new piece of information or a screenshot to make it worth the notification.
Section 5: Culture of Gratitude
5.1. Give Credit Where It’s Due
If someone's advice saved your day, tell them!- A Simple Thanks: A quick "That worked, thanks!" validates the contributor and lets others know the solution is solid.
Summary: The "Good Citizen" Checklist
| Instead of... | Try this... |
| Starting a new thread for a quick question. | Searching for an existing topic first. |
| Reacting with anger to a confusing post. | Asking a clarifying question first. |
| Posting a generic "I disagree." | Explaining why and offering an alternative logic. |
| Posting a wall of text. | Using headers, bolding, and lists to make it scannable. |
V 0.1
Last edited: