Slack Conventions

Standards for organising and using Slack at Tangible.

Channel Naming Prefixes

All channels should use a standardised prefix to keep the workspace organised and predictable. Slack automatically adds a dash after the prefix.

Prefix	Purpose	Example
`ask—`	Individual-led knowledge-sharing and Q&A	`#ask-julia`
`chatter—`	Informal topical conversation	`#chatter-music`
`delegation—`	Delegating unassigned work	`#delegation-backend`
`docs—`	Process documentation and reference notes	`#docs-pm-processes`
`feed—`	Automated feeds from external sources	`#feed-github`
`filipino—`	Discussions in Tagalog	`#filipino-backend`
`french—`	Discussions in French	`#french-general`
`inspo—`	Interesting concepts, visuals, and ideas (no immediate action required)	`#inspo-design`
`internal—`	Internal project discussions and collaboration	`#internal-lms`
`meetup—`	Team meet-up planning	`#meetup-2025`
`news—`	Updates directed at the team	`#news-product`
`notify—`	Communicating status, availability, etc.	`#notify-out-of-office`
`planning—`	Discussion channels where plans are formed	`#planning-delegation`
`review—`	Requesting code, copy, communication, or other review	`#review-communication`
`romanian—`	Discussions in Romanian	`#romanian-general`
`school—`	Sharing learning resources and office hour availability changes	`#school-backend`
`team—`	Updates and work from a department or team	`#team-project-managers`
`topic—`	Actionable topical discussions and strategy (not project-specific)	`#topic-accessibility`
`w—`	Client project channels	`#w-clientname`
`x—`	External channels (Slack Connect with clients/partners)	`#x-clientname`

When creating a new channel:

Channels sort alphabetically by prefix, so related channels group together
Client project channels (w—) sort near the end of the list
Use Slack sections to further organise your sidebar by grouping channels you frequently use