Update the Slack Integration

docs/getting-started.md

@@ -62,7 +62,7 @@ Atomist is now tracking new container images.  This includes updates to bills of
 Teams use Atomist to protect downstream workloads from new vulnerabilities.  It's also used to help teams track and remediate new vulnerabilities that impact existing workloads.  In the next sections, we'll look at how teams can use atomist to gain visibility into container workload systems like Kubernetes.
 
 * [Set up Checks](getting_started/checks.md) that will run whenever a new Image is pushed to your registry
+* [Create a Slack notification channel](integration/slack.md) to receive notifications about new security advisories impacting workloads.
 * Atomist watches for new advisories from [public sources](getting_started/sources.md), but you can also add your own internal advisories.  Checkout how to [get started with your own advisories](getting_started/private-advisories.md).
-* Add a [gitops controller](getting_started/pull-oriented.md) like [Flux](https://www.weave.works/oss/flux/) to pull candidate images that have passed their checks.
-* Use [kubernetes admission control](getting_started/admission-control.md) to ensure that images are fully checked before being admitted into different clusters or namespaces.
+* Use [kubernetes admission control](integration/kubernetes.md) to ensure that images are fully checked before being admitted into different clusters or namespaces.
 * Try adding another check to add [secret scanning](getting_started/add-secret-scanner-check.md) to make sure that the sources used to build an image are always scanned for leaked secrets.

docs/integration/slack.md

@@ -1,48 +1,50 @@
 # Slack
 
 Atomist has a powerful Slack integration to help your team leverage
-the power of ChatOps.  Select the Slack channels where you'd like to
-receive notifications when a given skill runs, and issue commands from
-chat that run skills.
+the power of ChatOps.  After installing the bot, you'll need to link
+some channels to GitHub repos.  The bot will only create notifications
+in channels that have subscribed to them.
 
-Here is a video walking you through setting up the Atomist Slack
-integration.
+Start by installing the GitHub Notifaction Skill.  [Click here to start the install](https://go.atomist.com/catalog/skills/atomist/github-notifications-skill).
 
-<div style="text-align:center;">
-  <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/hSbPQn4ncUs" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
-</div>
+![start-enable](img/slack/0-skill-start-enable.png)
 
-Start here:
-
-https://vonwig.slack.com/apps/A0HM83NCC-atomist?tab=more_info
+Use the "Continue" button on the right.
 
 ## Connect to Slack
 
-1.  From **Manage > Integrations**, choose the Slack integration.
-2.  Click **Connect to Slack** and follow the Slack authorization
-    flow. You will be adding the [Atomist Slack app][slack-app] to
-    your Slack workspace.
-
-[slack-app]: https://slack.com/apps/A0HM83NCC-atomist (Atomist Slack App)
+In the next step, you'll be redirected to Slack so that you can install the Atomist application 
+into your workspace.  This step can only be performed by a Slack user that has permission
+to install new applications in the Slack workspace.
+
+### 1. Redirect to Slack
+
+![choose-slack](img/slack/1-skill-choose-slack.png)
+
+### 2. Authorize the application
+
+![redirect-to-slack](img/slack/2-redirect-to-slack.png)
 
-## Linking Channels
+### 3. Redirect back to Atomist
 
-Once your Slack integration is complete, you will need to link
-channels to your GitHub repositories so that you receive notifications
-in the right channels.
+After being redirected back to Atomist, you'll be asked to link a channel to one of your GitHub repositories. 
+
+![redirect-to-slack](img/slack/3-link-channels.png)
+
+[slack-app]: https://slack.com/apps/A0HM83NCC-atomist (Atomist Slack App)
 
--   If you have not yet enabled the [GitHub integration][github],
-    you'll need to do so before you can link channels.
 -   Select a **Slack Channel** on the left, and one or more
     **Repositories** on the right, then click the **Link** button.
 -   You can always add, edit and remove channel links in the **Manage
     > Integrations > Slack** page.
 -   The `@atomist` bot will automatically be invited to linked channels.
 
-![Linking Slack channels and GitHub Repositories](img/slack/slack-channel-linking.png)
-
 [github]: github.md (Atomist GitHub Integration)
 
+### 4.  Complete Installation
+
+![4-set-params](img/slack/4-set-params.png)
+
 ## Disconnecting Slack
 
 You might want to disconnect Slack when:

mkdocs.yml

@@ -43,8 +43,8 @@ nav:
       - Getting Started: getting-started.md
       - Image Checks: getting_started/checks.md 
       - Creating Advisories: getting_started/private-advisories.md
-      - Gitops (pull-oriented delivery): getting_started/pull-oriented.md
-      - Kubernetes Admission Control: getting_started/admission-control.md
+      # - Gitops (pull-oriented delivery): getting_started/pull-oriented.md
+      - Kubernetes Admission Control: integration/kubernetes.md
       - Add secret scanning: getting_started/add-secret-scanner-check.md
       # - Adding Falco: getting_started/falco.md 
 
@@ -63,7 +63,7 @@ nav:
       - Linking images to commits: integration/linking-images.md
       - Tracking image deployments: integration/deploys.md
       # - GitHub: integration/github.md
-      # - Slack: integration/slack.md
+      - Slack: integration/slack.md
       # - Authentication Providers: 
           # - SAML: integration/saml.md
 #  - Tutorials: