Updating Community Management Discord, Telegram, & X (Twitter) Guides.mdx

[NFTDreww]

I have updated the overall update overview to be more inline with the feedback given over the past few weeks, which were:

Reframe the intro as a wayfinding statement. Instead of opening with a content summary, open with a one- or two-sentence orientation about what community security covers and where to go. Something like: "Community Management security spans several disciplines — each with its own dedicated Framework. Use this page to find the right one."

Convert the best practices section into a visual index. Each of the four sections (2FA/passwords, phishing, OpSec, emergency response) already has a corresponding Framework, so we can turn them into explicit cards or a linked table with the topic, a single descriptive sentence, and the link. This keeps the content without making it feel like a dead end.

Cut the inline detail that lives somewhere else. For example, TOTP configuration advice, the password manager separation rule, and the DM-first policy all belong in the destination frameworks, not here. Keeping it here creates both a maintenance burden for your team and dilutes the "go there for more" message.

------------------------------------------------------------------------ Therefore I was able to make the community manage guides more of the why, what, and how/where? Explaining this information and then leading into the actual frameworks for each that ALL needs to be taken into consideration when talking about community management and it's subsequent guides/frameworks.

This included a complete reformat of the Discord page, that I think addresses all feedback and has a cleaner flow to providing the north star for this section.

Frameworks PR Checklist

Thank you for contributing to the Security Frameworks! Before you open a PR, make sure to read information for contributors and take a look at the following checklist:

• Describe your changes, substitute this text with the information
• If you are touching an existing piece of content, tag current contributors from the attribution list
• If there is a steward for that framework, ask the steward to review it
• If you're modifying the general outline, make sure to update it in the vocs.config.ts adding the dev: true parameter
• If you need feedback for your content from the wider community, share the PR in our Discord
• Review changes to ensure there are no typos; see instructions below.

[frameworks-volunteer]

Model: z-ai/glm-5.2 Reasoning: medium Provider: openrouter

Security review: no issues found. No secrets, no injection vectors, no unsafe content. All links point to the official frameworks.securityalliance.dev domain. MDX is static content with no dynamic input.

QA review -- content aligns well with the PR description (wayfinding intros, visual index tables, cut inline detail). A few minor inconsistencies to address:

1. TagList component removed from discord.mdx but kept in telegram.mdx and twitter.mdx. All three pages should be consistent -- either keep TagList on all or remove from all.

2. Contributors not updated in twitter.mdx. NFTDreww was added to the wrote role in discord.mdx and telegram.mdx but not in twitter.mdx, despite content changes to that file.

3. "screenshot" (discord.mdx, line in risk table) vs "screenshotted" (twitter.mdx, same context). Pick one form for consistency.

4. Telegram.mdx: "two-step verification and phone number privacy in particular; take under five minutes" -- the semicolon should be a comma or em-dash, not a semicolon.

5. Links changed from relative paths (/guides/account-management/discord) to absolute URLs (https://frameworks.securityalliance.dev/guides/account-management/discord). This works but breaks the pattern used by the original files and other pages in the repo. Consider keeping relative paths for internal links.

None of these are blocking. The content itself is well-structured and security-appropriate.