Add ToC and relocate slack requests

1 files changed, 84 insertions, 63 deletions

diff --git a/communication/slack-guidelines.md b/communication/slack-guidelines.md
index 4d2bb43b..630f045a 100644
--- a/communication/slack-guidelines.md
+++ b/communication/slack-guidelines.md
@@ -8,6 +8,23 @@ are over 50,000 members who should all expect to have a positive experience.
 Chat is searchable and public. Do not make comments that you would not say on a
 video recording or in another public space. Please be courteous to others.
 
+- [Code of Conduct](#code-of-conduct)
+- [Admins](#admins)
+- [General Communication Guidelines](#general-communication-guidelines)
+  - [Workspace Channel History](#workspace-channel-history)
+  - [DM (Direct Message) Conversations](#dm-direct-message-conversations)
+  - [Specific Channel Rules](#specific-channel-rules)
+  - [Escalating and/or Reporting a Problem](#escalating-andor-reporting-a-problem)
+- [Requesting a Channel](#requesting-a-channel)
+- [Requesting a Bot, Token, or Webhook](#requesting-a-bot-token-or-webhook)
+- [Moderation](#moderation)
+  - [Admin Expectations and Guidelines]()
+  - [Sending Messages to the Channel]()
+  - [Processing Slack Requests](#processing-slack-requests)
+    - [Processing Channel Requests](#processing-channel-requests)
+    - [Processing Bot, Token, or Webhook Requests](#processing-bot-token-or-webhook-requests)
+  - [Inactivating Accounts](#inactivating-accounts)
+
 
 ## Code of Conduct
 
@@ -65,7 +82,10 @@ development to kubernetes,
 
 ### Escalating and/or Reporting a Problem
 
-Join the `#slack-admins` channel or contact one of the admins in the
+Join the `#slack-admins` channel and alert the admins to the current issue. This
+is the **fastest way** to get an admin response with many watching the channel.
+
+As a last resort, or if the issue is private, contact one of the admins in the
 [closest timezone][admins] via DM directly and describe the situation. If the
 issue can be documented, please take a screenshot to include in your message.
 
@@ -77,14 +97,69 @@ and describe the situation.
 
 ---
 
+## Requesting a Channel
+
+- Create a [GitHub Issue] using the Slack Request template.
+- Include the desired name of the channel. Typical naming conventions follow:
+  - `#kubernetes-foo`
+  - `#sig-foo`
+  - `#meetup-foo`
+  - `#location-user`
+  - `#projectname`
+- In the issue describe the purpose of the Channel. Channels should be
+  dedicated to [SIGs, WGs, UGs][sig-list], sub-projects, community topics, or
+  related Kubernetes programs/projects.
+  - Linking to resources such as the PR adding the subproject will speed in the
+    validation and processing of the channel creation request.
+  - Channels are **NOT**:
+    - Company specific; cloud providers are ok with product names as the channel.
+      Discourse will be about Kubernetes-related topics and not proprietary
+      information of the provider.
+    - Private channels with the exception of: code of conduct matters, mentoring,
+      security/vulnerabilities, github management, or steering committee.
+  - Special accommodations will be made where necessary.
+
+After you submit your request the Slack admins will review and follow-up with
+any questions in the issue. If two admins add their support for the creation of
+the channel, an admin will assign it to themselves and close the issue once it
+has been created.
+
+
+## Requesting a Bot, Token, or Webhook
+
+**READ BEFORE SUBMITTING A REQUEST**
+
+Bots, tokens, and webhooks are reviewed on a case-by-case basis with most
+requests being rejected due to security, privacy, and usability concerns. Bots
+and the like tend to make a lot of noise in channels. The Kubernetes Slack
+instance has over 50,000 members and it is the role of the Slack admins to
+ensure everyone has a great experience.
+
+Typically approved requests include: GitHub, CNCF requests, or other
+tools/platforms used to aid in the management of Slack itself.
+
+- Create a [GitHub Issue] using the Slack Request template.
+- In the description, describe the request, its intended purpose and benefit to
+  the community. Supplying links to supporting content such as a document
+  outlining what OAuth scopes that are requested, and why are
+  **STRONGLY ENCOURAGED**.
+
+After you submit your request the Slack admins will review and follow-up with
+any questions in the issue. If consensus can be reached among the admins, the
+request will be approved and follow-up communication on implementation will be
+discussed in Slack itself.
+
+---
+
 ## Moderation
 
 ### Admin Expectations and Guidelines
 
 Admins should adhere to the general Kubernetes project [moderation guidelines].
 
-Admins should additionally make sure to mention they are a Slack admin and their
-timezone in their “What I do” section of their Slack profile.
+Additionally, admins should ensure they have 2-factor auth enabled for their
+account and mention they are a Slack admin in the "What I do" portion of their
+profile. This message should also include the timezone they are representing.
 
 Be mindful of how you handle communication during stressful interactions.
 Administrators act as direct representatives of the community, and need to
@@ -95,9 +170,9 @@ a great time to enlist the help of another admin.
 Try to take any situations that involve upset or angry members to DM or video
 chat. Please document these interactions for other Slack admins to review.
 
-Content will be automatically removed if it violates code of conduct or is a
-sales pitch. Admins will take a screenshot of such behavior in order to document
-the situation. The community takes such violations extremely seriously, and the
+Content will be removed if it violates code of conduct or is a sales pitch.
+Admins will take a screenshot of such behavior in order to document the
+situation. The community takes such violations extremely seriously, and the
 admins are empowered to handle it swiftly.
 
 
@@ -108,13 +183,13 @@ notifications from these commands. Remember Kubernetes is a global project -
 please be kind.
 
 
-### Slack Requests
+### Processing Slack Requests
 
 Admins are tasked with processing requests for channels and other things such as
 bots, tokens or webhook.
 
 
-#### Channel Requests
+#### Processing Channel Requests
 
 Channel requests should be reviewed for their relation and relevance to the
 Kubernetes community. Typically channels should be dedicated to SIGs, WGs, UGs,
@@ -141,7 +216,7 @@ Contact conduct@kubernetes.io or an admin in the #slack-admins channel if there
 ```
 
 
-#### Bot, Token, or Webhook Requests
+#### Processing Bot, Token, or Webhook Requests
 
 Requests should first be evaluated for their relevance to the project. Typically
 approved requests are related to: GitHub, the CNCF, or other tools/platforms
@@ -168,60 +243,6 @@ inactivated accounts] for more information.
 - Not adhering to the code of conduct set forth in DMs and/or channels.
 - Overtly selling products, related or unrelated to Kubernetes.
 
----
-
-## Requesting a Channel
-
-- Create a [GitHub Issue] using the Slack Request template.
-- Include the desired name of the channel. Typical naming conventions follow:
-  - `#kubernetes-foo`
-  - `#sig-foo`
-  - `#meetup-foo`
-  - `#location-user`
-  - `#projectname`
-- In the issue describe the purpose of the Channel. Channels should be
-  dedicated to [SIGs, WGs, UGs][sig-list], sub-projects, community topics, or
-  related Kubernetes programs/projects.
-  - Linking to resources such as the PR adding the subproject will speed in the
-    validation and processing of the channel creation request.
-  - Channels are **NOT**:
-    - Company specific; cloud providers are ok with product names as the channel.
-      Discourse will be about Kubernetes-related topics and not proprietary
-      information of the provider.
-    - Private channels with the exception of: code of conduct matters, mentoring,
-      security/vulnerabilities, github management, or steering committee.
-  - Special accommodations will be made where necessary.
-
-After you submit your request the Slack admins will review and follow-up with
-any questions in the issue. If two admins add their support for the creation of
-the channel, an admin will assign it to themselves and close the issue once it
-has been created.
-
-
-## Requesting a Bot, Token, or Webhook
-
-**READ BEFORE SUBMITTING A REQUEST**
-
-Bots, tokens, and webhooks are reviewed on a case-by-case basis with most
-requests being rejected due to security, privacy, and usability concerns. Bots
-and the like tend to make a lot of noise in channels. The Kubernetes Slack
-instance has over 50,000 members and it is the role of the Slack admins to
-ensure everyone has a great experience.
-
-Typically approved requests include: GitHub, CNCF requests, or other
-tools/platforms used to aid in the management of Slack itself.
-
-- Create a [GitHub Issue] using the Slack Request template.
-- In the description, describe the request, its intended purpose and benefit to
-  the community. Supplying links to supporting content such as a document
-  outlining what OAuth scopes that are requested, and why are
-  **STRONGLY ENCOURAGED**.
-
-After you submit your request the Slack admins will review and follow-up with
-any questions in the issue. If consensus can be reached among the admins, the
-request will be approved and follow-up communication on implementation will be
-discussed in Slack itself.
-
 
 [coc]: /code-of-conduct.md
 [admins]: ./moderators.md#Slack