Costa Rica
Last updated: 2026-04-08
This page describes the category setup for this organization’s GitHub Discussions hub.
| Section | Categories (type) | When to use it | Examples / best practices |
|---|---|---|---|
| Community | - General (Discussion) - Show and tell (Discussion) - Polls (Poll) - Events (Discussion) |
- General: anything community/meta that doesn’t fit elsewhere - Show and tell: demos, write-ups, integrations, things you built - Polls: quick votes to guide priorities (“next livestream topic?”, “next feature?”) - Events: meetups/livestreams/webinars and follow-ups |
- General titles: “How should we organize learning paths?”, “Introduce yourself + what you’re building” - Show and tell: include a link/screenshot + short “how it works” + what you used from the provided materials - Polls: keep options mutually exclusive (3–6), set a close date, and comment with the decision afterward - Events: include date/time + timezone, agenda/link, and ask for RSVP via 👍 or a comment |
| Product | - Announcements (Announcement) - Ideas (Discussion) |
- Announcements: official updates from maintainers (releases, policy changes, roadmap milestones) - Ideas: suggestions and improvement proposals |
- Announcements: start with a 2–3 line TL;DR; link to docs/issues; pin major updates if needed - Ideas: use a simple structure (problem → proposal → trade-offs); include success criteria so others can evaluate it |
| Support | - Q&A (Q&A) - Support / Troubleshooting (Q&A) |
- Q&A: questions that should end with a clear accepted answer (how-to, “what’s the right way?”) - Support / Troubleshooting: longer back-and-forth debugging threads and ongoing issues |
- Q&A: ask one clear question, share what you tried, and mark an accepted answer when solved (plus a short resolution summary) - Troubleshooting: include expected vs actual, repro steps, environment/versions, and logs (redact secrets); summarize the root cause/fix at the end |
Refresh Date: 2026-04-08