Skip to content

Document dashboard placement of status and Discord tools #314

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
demassimo wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Document dashboard placement of status and Discord tools #314

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,10 @@ that together provide a management dashboard for Rust game servers.
## Documentation expectations

When you add or modify modules, consult `docs/module-architecture-guide.md` for placement rules and update it if you introduce a
new pattern. Keep `docs/module-usage-report.md` aligned with the current code so that unused files are easy to spot.
new pattern. Keep `docs/module-usage-report.md` aligned with the current code so that unused files are easy to spot. Note that the
Rust server status surface lives exclusively under the **Server workspace → Settings** view, while the Discord ticketing and
authentication tools remain anchored to the main dashboard's **Discord** tab—documentation should reflect those established UI
locations.

## Coding conventions

Expand Down
5 changes: 4 additions & 1 deletion docs/module-usage-report.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
# Module usage report

This document summarises how the major backend and frontend modules are referenced so we can spot redundant code paths.
This document summarises how the major backend and frontend modules are referenced so we can spot redundant code paths. Remember
that the Rust server status interface is intentionally scoped to the **Server workspace → Settings** view, and the Discord ticket
queue plus linked-account authentication tools are concentrated in the main dashboard's **Discord** tab; keep those placements in
mind when reviewing module wiring.

## Backend modules

Expand Down