Documentation / Posting Guidelines

Posting Guidelines

What makes great content and when to share it

The Core Idea

Vibe9 exists so developers don't have to reinvent the wheel. Every post should help someone skip a struggle, learn something valuable, or find inspiration.

Ask yourself: "Would this have saved me time or frustration if I'd found it earlier?" If yes, it probably belongs here.

When to Share

Major Revelations

You just figured something out that changed how you think about a problem. The "aha!" moment that makes everything click.

Hard-Won Lessons

You spent hours (or days) debugging something. You finally solved it. Save others from that pain.

Non-Obvious Solutions

The answer wasn't in the first Stack Overflow result. You had to dig, experiment, or piece together info from multiple sources.

Something You Built

A project, tool, or experiment - even if it's unfinished. Share the journey, get feedback, inspire others.

Questions That Need Discussion

Architecture decisions, best practices debates, "how would you approach this?" - the forum is perfect for these.

What Doesn't Fit

"Hello World" Content

Basic tutorials that are already covered extensively elsewhere. Unless you have a genuinely new angle or insight.

Promotional Spam

"Buy my course" or "Use my SaaS" without genuine value. Showcasing your project is fine; spamming isn't.

AI-Generated Filler

Content that's obviously just AI output without real experience behind it. Your AI can help you write, but the insights should be yours.

Duplicate Posts

Posting the same thing multiple times or across multiple categories to get more visibility.

By Content Type

Articles

In-depth content: tutorials, guides, opinions, analysis.

  • • Should teach something substantial or offer a unique perspective
  • • Include code examples where relevant
  • • Explain the "why" not just the "how"
  • • Minimum ~500 words of real content (quality over quantity)

Lessons Learned

Real experiences: what you tried, what failed, what worked.

  • • Be specific about the context and the problem
  • • Share what you actually tried (including what didn't work)
  • • Include the solution with enough detail to reproduce
  • • Distill it to a clear takeaway

Showcase

Projects at any stage: ideas, WIP, launched, growing.

  • • Describe what it does and who it's for
  • • Share the tech stack and interesting decisions
  • • Be honest about the stage it's at
  • • If you want feedback, be specific about what kind

Forum Posts

Discussions, questions, finds, and conversation.

  • • Use a descriptive title (not just "Help!")
  • • Provide context - what you're trying to do, what you've tried
  • • For questions, include relevant code or error messages
  • • Choose the right category

The Quality Bar

All content goes through admin review before publishing. We're looking for:

Genuine Value

Would you be glad to find this if you were searching for help on this topic?

Clear Writing

Can someone understand what you're saying without re-reading it three times?

Real Experience

Is there actual knowledge behind this, or is it just regurgitated content?

Effort

Did you put care into this? Proofread? Format the code properly?

Note: We'll work with you if something needs tweaks. Rejection isn't personal - we want to help you make it better.

🤖 Writing with AI

Vibe9 is built for AI-assisted publishing. Using your AI to help write is not only allowed - it's encouraged! But there's a difference between AI-assisted and AI-generated.

✓ AI-Assisted

  • • You have the experience/insight
  • • AI helps you articulate it clearly
  • • You review and refine the output
  • • The knowledge is genuinely yours

✗ AI-Generated Filler

  • • "Write me an article about React"
  • • No personal experience behind it
  • • Generic content anyone could generate
  • • Posted without real review

The test: If someone asked you follow-up questions about your post, could you answer them from experience? If yes, you're good.

Quick Reference

Scenario Best Place
"I just figured out how to do X properly" Lessons Learned
"Here's a deep dive on topic Y" Article
"Check out this tool I'm building" Showcase
"How would you approach this problem?" Forum (Help & Support)
"Found this cool library/resource" Forum (Interesting Finds)
"Quick debugging tip that saved me" Lessons Learned
"General discussion about dev life" Forum (General or Off Topic)

Ready to Share?

Got something valuable? The community is waiting.