How we write these
A guide is only useful if it works on the first attempt, on the version of Discord you are actually looking at. Four rules follow from that.
Every step is performed, not imagined
Procedures are written while doing them. If a menu has moved or a setting was renamed, the guide says what it is called now, not what it used to be called.
Prerequisites come first
Nothing is worse than reaching step six and discovering you needed Manage Roles. Required permissions and settings are stated before the first step, not buried inside it.
Failure modes are part of the guide
Where a step commonly does not work, the guide says so and says why. A procedure that only documents the happy path is half a procedure.
We date what we checked
Discord changes its interface without notice. Each guide carries the date it was last checked against the live client, so you can judge whether to trust the screenshots.
Disclosure. Guides are written in-house with AI assistance in drafting, then checked against the product. We do not attach invented author names or fictional credentials to anything we publish.