How to post smart: picking the right type and writing a great post

Choosing the right post type increases your chances of getting the result you want and keeps the community organized.

Question (Q&A)

Goal is one clear answer or solution; a “best answer” can be marked; use for error messages, settings, how-to questions.

Conversation (Discussion)

Goal is to exchange ideas, compare approaches, or brainstorm; multiple valid perspectives, no single “best answer”; use for comparing workflows, exploring roadmap wishes, sharing experiences.

Checklist for a powerful post

• Catchy, specific title: short and clear (e.g. “SLA Escalation: ticket stays in queue after 15 min”).
• Context: environment, version, role, and goal — what do you want to achieve, and why?
• What you've tried: steps, settings, scripts, documentation.
• Evidence: anonymized screenshots, error messages, log snippets.
• Clear question: “Which setting am I missing?” / “What's a better workflow for…?”
• Tags: add 3–5 relevant tags (e.g. SLA, workflow, API).
• Structure: use line breaks and bullet points — make it easy to scan.

Replying well

Understand the question (summarize it in one sentence to avoid misunderstandings), be specific (share steps, settings, or a mini how-to), explain the “why” (helps others learn and reduces trial-and-error), and link to sources (documentation, release notes, related topics). Keep it friendly — assume good intentions, ask clarifying questions if needed.

Replying to a specific comment

In a busy topic, you don't have to reply to the whole thread — you can reply directly to one specific comment. Your response is then nested right underneath it, so related exchanges stay together even when several side discussions are running at once. Threads go three levels deep; reply to something already at the deepest level and your response is added just below it with an automatic mention, so the connection isn't lost. Older topics keep working as before and stay in their flat format until someone posts a new nested reply, at which point the thread structure kicks in for that topic.

Keep the discussion flowing

@mention colleagues or experts with relevant experience, ask deeper questions, and build on others' input by confirming working steps and adding variations. When the original poster confirms a solution or marks an answer, add a short summary for future readers.

Do's & don'ts

Do focus on one topic per post, thank those who help, and mark the solution. Don't share screenshots with personal data, or post vague complaints without details.