Updating Community Management Discord, Telegram, & X (Twitter) Guides.mdx#514
Closed
NFTDreww wants to merge 6 commits into
Closed
Updating Community Management Discord, Telegram, & X (Twitter) Guides.mdx#514NFTDreww wants to merge 6 commits into
NFTDreww wants to merge 6 commits into
Conversation
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.
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.
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.
NFTDreww
changed the title
NFTDreww
changed the title
frameworks-volunteer
left a comment
frameworks-volunteer
left a comment
Collaborator
There was a problem hiding this comment.
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:
-
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.
-
Contributors not updated in twitter.mdx. NFTDreww was added to the
wroterole in discord.mdx and telegram.mdx but not in twitter.mdx, despite content changes to that file. -
"screenshot" (discord.mdx, line in risk table) vs "screenshotted" (twitter.mdx, same context). Pick one form for consistency.
-
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.
-
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.
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
Collaborator
|
@NFTDreww for my understanding this is a duplication of the #513 with the only addition of the twitter file, am i right? If yes, can you please add that file there as i've already made a lot of changes regarding the files structure and it would be a repetition here. Thanks!🙏🏻 If we can make the #513 merge today or tomorrow, these updated will be into our monthly update of the .org site :) |
Collaborator
|
Model: @scode2277 Confirmed — I compared both diffs and #514 is largely a duplicate of #513 for discord.mdx and telegram.mdx, with twitter.mdx as the only net-new file. File overlap:
The discord and telegram content is substantively the same across both PRs (same risk tables, topic indexes, community manager sections), but there are divergences that would need resolving if consolidating:
Recommendation: agree with consolidating into #513. If @NFTDreww moves the twitter.mdx changes to #513 (matching #513's conventions: relative links, AttributionList, lowercase contributor handle), #514 can be closed to avoid the maintenance burden of two parallel PRs touching the same files. |
NFTDreww
added a commit
to NFTDreww/frameworks
that referenced
this pull request
Jul 7, 2026
Adjusted to fixes called out in security-alliance#513 to flesh with security-alliance#514
NFTDreww
added a commit
to NFTDreww/frameworks
that referenced
this pull request
Jul 7, 2026
Updating fixed to this to address call outs from security-alliance#513 & security-alliance#514
Adjusted for call outs in security-alliance#513 and security-alliance#514
9 tasks
Update twitter.mdx
NFTDreww
added a commit
to NFTDreww/frameworks
that referenced
this pull request
Jul 7, 2026
Updating Twitter to address call outs in security-alliance#513 and security-alliance#514
Collaborator
Author
6 tasks
mattaereal
pushed a commit
that referenced
this pull request
Jul 8, 2026
* Update overview.mdx I have updated the overall update overview to be more inline with the feedback given over the past few weeks, which were: 1) 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." 2) 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. 3) 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 this page, that I think addresses all feedback and has a cleaner flow to providing the north star for this section. * Update discord.mdx 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 this page, that I think addresses all feedback and has a cleaner flow to providing the north star for this section. * Update telegram.mdx 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 this page, that I think addresses all feedback and has a cleaner flow to providing the north star for this section. * Update slug to make attribution list visible * Update slug to make contributor profile visible * Remove manually added contribute call * Update docs/pages/community-management/overview.mdx * Update docs/pages/community-management/telegram.mdx * Update docs/pages/community-management/discord.mdx * Update docs/pages/community-management/discord.mdx * Update docs/pages/community-management/overview.mdx * Update docs/pages/community-management/telegram.mdx * Update docs/pages/community-management/telegram.mdx * Update docs/pages/community-management/telegram.mdx * Remove components * Update links to make them relative in the discord file * Update links to make them relative in the overview file * Update links to make them relative in the telegram file * Remove call to contribution line from discord file * Update twitter.mdx Updating fixed to this to address call outs from #513 & #514 * Remove manually added contribution call --------- Co-authored-by: Sara Russo <sararusso984@gmail.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
3 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.
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:
vocs.config.tsadding thedev: trueparameter