feat: replace Slack mentions with Discord - #19
Merged
Merged
Conversation
thevvalverde
force-pushed
the
feat/slack-to-discord
branch
from
September 15, 2026 14:44
f21b225 to
f5bd94d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces every Slack reference in the site content and repo docs with Discord, ahead of the DjangoCon Europe 2027 community server replacing Slack.
The invite link used throughout is the one added to
navigation.json(social_media.discord).Changes
Content pages — direct Slack → Discord swaps:
information/social_events/0_soon.mdtalks/selection_process/2_selection_process.mdtalks/cfp/0_cfp.md(both mentions)talks/cfp/1_schedule.mdConduct pages — reworded rather than swapped, since Slack's
#care-teamchannel has no direct Discord equivalent:code_of_conduct.md: "By Slack: direct message any member of the #care-team channel" → "By Discord: direct message any member carrying the CARE role on our Discord server."response_guide/3_care_team.md: "via the #care-team Slack channel" → "by direct message to a CARE member on Discord."response_guide/4_communications_protocol.md: three mentions (don't speculate on Discord / rumor on Discord / general organizer Discord channel).Repo docs —
CODE_OF_CONDUCT.md(2 mentions).CODE_REVIEW.mdhad a stale finding claiming two divergent Slack invite tokens were in use;cfp/0_cfp.mdactually used the same token as everywhere else, so that bullet was rewritten to describe the real remaining issue — the invite is hard-coded per page instead of read fromnavigation.json.Assets —
logo_slack.svgremoved,logo_discord.svgadded. The footer builds icon paths dynamically from thesocial_mediakeys (logo_ + key + .svg), so the Discord icon is picked up automatically and nothing referenced the Slack file once the key changed.Verification
Rendered
/,/conduct/code_of_conduct/,/conduct/response_guide/,/information/social_events/,/talks/cfp/,/talks/selection_process/— all 200. Confirmed the Discord link andlogo_discord.svgappear in the rendered output, and the string "slack" no longer appears in any rendered page.tests/test_seo.pywas not run — pytest isn't installed in the active interpreter.Follow-up (not in this PR)
The Discord URL is now repeated in eight content files. Wiring content to read
social_media.discordfromnavigation.jsonwould make a future invite change a one-line edit; that needs a template change, so it's left out of scope here.🤖 Generated with Claude Code