Conversation
The tree split "Discord Bot" from the feature sections, organising by surface. The product is not split that way — /configure server carries a "Manage on Website" button, and almost every task exists in both places — so a reader had to know which surface a capability lived on before they could find it. Configuration was documented twice; Guild League was one paragraph inside Signups and nothing else. Regrouped by job: Start Here, Events, Scores and VOD, Guild Tracker, Public Data, Configuration, Community, Reference. Each page covers a task and shows both paths to it. Sixteen pages added for areas that had no documentation at all: VOD Reviews, Guild League's web side, event types and signup profiles, platoons and function roles, waitlist and priority, the Platoon Builder, the website settings, the five public data pages, a glossary, an end-to-end first node war walkthrough, and a 404. Five pages retired, each after its replacement existed and its content was verified as migrated: bot/commands, bot/configuration, features/parties-and-waitlist, features/tierlists-and-stats and website/overview. Every command was checked against Discord's own command picker on a live Guild server rather than against the bot's built-in help, which omits five commands that exist and lists two that do not. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
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.
The complete refresh we talked about. One PR, as you asked.
The structural problem this fixes
The tree split
Discord Botfrom the feature sections, organising by surface. But the product isn't split that way —/configure serverhas a "Manage on Website" button, and almost every task exists in both places. So a reader had to already know which surface a capability lived on before they could find it.That produced real symptoms: configuration was documented in two places that didn't reference each other, and Guild League was one paragraph inside Signups and nothing else.
Regrouped by job: Start Here · Events · Scores and VOD · Guild Tracker · Public Data · Configuration · Community · Reference. Each page covers a task and shows both paths to it.
What had no documentation at all
Sixteen new pages. The ones most worth your eye:
vc,intervalandnodewar-slotsoptions, the four officer actions, and the public match browser and standings./priority view, which is the tool that answers "why did they get in and I didn't".Five pages retired
bot/commands,bot/configuration,features/parties-and-waitlist,features/tierlists-and-statsandwebsite/overview. Each was removed only after its replacement existed, and each removal got a review whose only job was proving nothing was lost — which caught two things that had been left behind and brought them back.How the commands were verified
Against Discord's own command picker on a live Guild server, not against the bot's
/help. That matters:/helpomits/signup gvg,/signup list,/scores menu,/scores uploadand/player profile, and lists/member registerand/attendance update, which don't exist. The reference now matches the 36 commands a Guild server actually registers.Two command groups are not verified and are marked as depending on server type: the Community commands and the Trial commands. They don't appear on a Guild server, so I had nothing to check them against.
Notes
npm run docs:buildpasses. VitePress fails on dead internal links, so a green build is also a link check across both locales.Written with AI assistance, verified command by command against the running product.
🤖 Generated with Claude Code