Last updated: June 2026
Our Community, Our Standards
The WebCommander Community Hub exists for one reason — to help developers, store owners, and agency partners build better, faster, and smarter on WebCommander. These guidelines exist to keep this space useful, respectful, and worth coming back to.
By participating, you agree to these guidelines. Repeated or serious violations may result in post removal, thread locking, or account suspension.
1. Be Helpful First
This is a community of practitioners. Everyone here is either trying to solve a problem or share a solution. Lead with helpfulness.
- Answer what was actually asked. Don't redirect someone to "just Google it" or "read the docs" without at least pointing them in the right direction.
- Share what you know. If you've solved something the hard way, write it up. Your war story is someone else's shortcut.
- Include context in your replies. A one-line answer with no explanation helps nobody. Show your reasoning.
2. Post in the Right Category
Threads posted in the wrong category will be moved by moderators without notice. Before posting, take 30 seconds to check the category descriptions.
3. Write a Good Thread Title
Your thread title is the first thing people see. A good title gets answers faster.
Do this:
✅ "Bulk order update API returning silent 'skipped' — no error code"
✅ "Best approach for multi-warehouse routing with customer tags?"
✅ "Product grid LCP over 6s on 250+ item category pages — what worked for you?"
Not this:
❌ "Help"
❌ "Not working"
❌ "Question about my store"
❌ "URGENT!!!"
If your title could apply to any forum on the internet, rewrite it.
4. Give Your Post Enough Detail
Vague posts get vague answers — or no answers at all. When asking for help, include:
- What you're trying to do — describe the goal, not just the symptom
- What you've already tried — saves everyone from suggesting things you've ruled out
- Your setup — relevant plan tier, plugins in use, custom code involved
- Error messages or logs — copy the exact text, don't paraphrase it
- Code snippets — use code blocks, not screenshots of code
// Use code blocks like this
{
"order_id": "ORD-00412",
"status": "processing"
}
The more specific your question, the faster and better your answers will be.
5. Keep It Constructive
Disagreement is fine. Disrespect is not.
- Critique ideas, not people. "I think that approach has a performance risk at scale" is fine. "That's a terrible idea" is not.
- No condescension toward beginners. Everyone was new once. If a question seems basic to you, either answer it helpfully or move on.
- No pile-ons. If someone has already been corrected, there's no need to add a fifth reply saying the same thing.
- Challenge politely. If you think an answer in this thread is wrong, say so — but explain why and offer a better path.
6. No Spam, Self-Promotion, or Solicitation
This forum is not an advertising platform.
- No unsolicited promotion of your own products, services, or agency — in posts, replies, or private messages.
- Relevant mentions are fine. If you built a plugin that directly answers someone's question, you can mention it — once, with full disclosure that it's yours.
- No affiliate links. Ever.
- No recruitment posts outside of designated community channels.
- No cross-posting the same question across multiple categories to increase visibility.
7. Respect Intellectual Property
- Do not share WebCommander source code, license keys, or proprietary template files that you are not authorised to distribute.
- When sharing code snippets from your own builds, make sure you have the right to share them — especially on client projects.
- Credit others when you build on their work. If you adapted someone's snippet from this forum, say so.
8. Sensitive Topics — Billing & Account Issues
For account-specific billing disputes, plan access issues, or anything involving your personal account data:
Do not post account details, invoice numbers, or payment information publicly.
Use the Billing & Plans category for general questions only. For account-specific issues, contact WebCommander Support directly at contact@webcommander.com.
9. Bug Reports — How to Do It Right
The Bug Reports & Issues category is monitored by the WebCommander team. To get a faster response:
- Check if it's already been reported before posting — search the category first.
- Include your plan tier and whether the issue is on a live store or staging environment.
- Provide reproduction steps — numbered, specific, repeatable.
- One bug per thread. Don't bundle multiple issues into a single report.
10. Moderator Decisions Are Final
The WebCommander Community Hub is moderated by a mix of WebCommander staff and appointed community moderators. Moderators may:
- Edit post titles for clarity
- Move threads to the correct category
- Remove posts that violate these guidelines
- Lock threads that have run their course
- Issue warnings or suspend accounts for repeated violations
If you believe a moderation decision was made in error, contact the moderation team via direct message — do not dispute it publicly in the thread.
The Short Version
Be helpful. Be specific. Be respectful. Post in the right place. Don't spam.
If you're genuinely here to learn and contribute, you'll fit right in.
Questions About These Guidelines?
Post in the Community & Off-Topic category with the tag [guidelines] and a moderator will respond.
These guidelines are reviewed periodically and may be updated. Significant changes will be announced in the Community & Off-Topic category.
— The WebCommander Community Team
