Repository navigation
chore: remove Discord from doc website (GTM-1636) - #213
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
leorossi
force-pushed
the
gtm-1636-remove-discord-from-doc-website
branch
from
August 25, 2026 08:19
e190fdb to
cb255a6
Compare
mcollina
requested changes
Aug 25, 2026
mcollina
left a comment
mcollina
left a comment
Member
There was a problem hiding this comment.
The actual docs must be changed in platformatic/platformatic, here it’s only the footer.
Contributor
Author
|
That is already merged: platformatic/platformatic#5091 |
Member
|
This does not need to change the actual docs, that will come from an actual release |
Contributor
Author
|
This removes the Discord link from the previous versions, and, more important, from the docs website (check |
leorossi
force-pushed
the
gtm-1636-remove-discord-from-doc-website
branch
from
October 12, 2026 08:46
cb255a6 to
1000e80
Compare
mcollina
requested changes
Oct 12, 2026
Removes the Discord entry from the Docusaurus footer Community section and strips Discord links from the current docs and from the frozen 2.75.2 and 3.68.0 versioned snapshots, as part of sunsetting the Discord server. Ref: GTM-1636 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MjvfbjnNaNbEC6di1XiZmr Signed-off-by: Leonardo Rossi <leonardo.rossi@gmail.com>
leorossi
force-pushed
the
gtm-1636-remove-discord-from-doc-website
branch
from
October 12, 2026 09:38
1000e80 to
b062ae5
Compare
This branch was successfully deployed
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
2 participants
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.
Part of sunsetting the Discord server (GTM-1634).
Closes GTM-1636.
What changed — 35 files
docusaurus.config.jsSame edit shapes as the matching platformatic PR: community bullets deleted outright,
...or join our [Discord feedback] channel.clauses trimmed back to the GitHub issue link, and the one sentence inoverview/what-is-watt.mdthat offered both Discord and GitHub Discussions collapsed to just Discussions.Please read: overlap with platformatic/platformatic
docs/**in this repo is generated —platformatic/platformaticpushes tomainunderdocs/**fire a repo-dispatch that runsrebuild-and-deploy-docs.ymlhere, which regeneratesdocs/and auto-commits.So the 13 files under
docs/here are also fixed at the source in platformatic/platformatic#5091. They're included in this PR anyway so the live site is clean immediately rather than waiting for the next sync, and so this PR leaves nodiscord.ggreference behind on its own.The other 22 files —
docusaurus.config.jsand bothversioned_docs/snapshots — are only fixable here; the sync never touches them.Merge order doesn't matter, but if the sync runs between the two merges it may produce a no-op commit over
docs/. Worth a glance at the generated commit afterwards.Verification
node --check docusaurus.config.jspasses. Zerodiscordreferences remain anywhere in the repo (case-insensitive, excludingnode_modules). Site build not run, per the ticket workflow — leaving that to CI.Note your local clone may have been on
version-3.57.0; this branch is cut from currentmain, which is on3.68.0.🤖 Generated with Claude Code
https://claude.ai/code/session_01MjvfbjnNaNbEC6di1XiZmr