Slack is a real-time chat platform owned by Salesforce, best known as workplace software — but many companies and open-source projects also run public, invite-open Slack workspaces as their community hub. It ranks #11 among developer community platforms at roughly 15.7% usage share, offering a more workplace-style, threaded alternative to Discord for professional and framework-specific discussion.
Public developer Slacks follow a predictable channel pattern. Read #announcements before asking anything (your question may already be answered there), introduce yourself in #introductions if it exists, and always ask technical questions in the specific topic channel rather than a general one — it gets you a faster, better-targeted answer and keeps the workspace searchable.
// typical public dev-community Slack channel layout
#announcements // read-only, official updates
#introductions // say hi, what you're building
#help // general support questions
#help-frontend // topic-specific support
#showcase // share what you shippedThere's no central Slack directory — you join through an invite link the community itself publishes, usually on the project's website, GitHub README, or docs footer. Anyone can generate one, so links do expire; if one is dead, check the project's GitHub Discussions or Twitter for a fresh one.
// invite links look like this and expire after a set time/uses
https://join.slack.com/t/workspace-name/shared_invite/zt-abc123xyz