Hello Nexus Community Members,
Tags are small, but mighty — they make the Nexus Community discoverable, searchable, and more valuable for everyone. Proper tagging ensures your post reaches the right experts, surfaces in relevant searches, and helps our community and product teams spot trends and prioritize improvements.
Why tagging matters
- Help the right people find your post: Tags connect your question or discussion to members who follow those topics (product areas, features, versions, integrations).
- Improve search and discovery: Posts with clear tags appear in relevant searches and saved searches, so answers and resources are easier to find later.
- Enable faster, better responses: Subject-matter experts and product teams filter by tags to triage and respond — good tags speed up time-to-answer.
- Power community analytics and product feedback: Trend analysis on tags helps identify recurring issues, feature requests, and gaps in documentation or training.
- Support notifications and saved searches: Users subscribing to tags receive updates on topics they care about, increasing engagement and knowledge sharing.
When to add tags
- Always — add at least one clear tag when posting a Question or Discussion.
- Include tags when updating a post (e.g., resolving an issue, adding an outcome) so future readers can find the final solution.
How to pick the right tags (best practices)
- Start broad, then narrow: Use a product-level tag (e.g., Skylar One) plus 1–2 specific area tags (e.g., discovery, automation, compliance).
- Include version or integration tags when relevant: If your issue is version-specific or involves an integration (e.g., ServiceNow, AWS), add that tag.
- Limit the number: 2–5 well-chosen tags are better than many vague ones — too many dilute the signal.
- Use established tags when possible: Check existing posts to match community conventions and improve visibility.
- Be specific for troubleshooting: For Questions, include environment details as tags (collector, API, alerting) so the right experts see it quickly.
Examples
- Collector fails to authenticate after upgrade → tags: skylar-one, collector, upgrade-9.5
- Best practices for scheduling reports → tags: reporting, automation, best-practices
- Ideas for a new integration → tags: ideas, integrations, servicenow
Community etiquette & tag maintenance
- If a moderator or community manager suggests a tag change, accept it — it helps keep the forum consistent.
- If your discussion evolves, update tags to reflect the final content (especially when marking an accepted answer).
- Suggest new tags if you see a gap — include a short rationale so moderators can evaluate adding them.
Quick checklist for tagging a post
- Pick the main product or platform tag.
- Add 1–2 area-specific tags (feature, function, or symptom).
- Add integration or version tags if relevant.
- Keep total tags between 2 and 5.
- Review existing tags and adapt to community conventions.
Want a short template to include with your posts that makes tagging easy? Reply below and I’ll share a quick copy-paste version you can use when creating Questions or Discussions.
Best regards,
Sara Leslie
Community Manager