Skip to content

Content guide

Content guide

Write content that can be discovered and discussed.

Titles

  • Describe the problem or result, not just “help” or “share”
  • Include version, environment, or industry keywords for search

Body

  • Start with context and goal, then approach and result
  • Mark code block languages; crop screenshots to key areas
  • Credit sources when quoting others

Tags

  • At most 5 #tags per post
  • Use stable, reusable topic words instead of one-off tags

Interaction

  • Give actionable replies
  • Accepted or helpful answers earn points and exposure
  • Avoid mutual likes, spam, and meaningless bumps
Switch to normal mode

Contents