Add docs for Slack integration

[mapsandapps]

Ticket is SVC-60.

[jennifer-shehane]

I made a few changes:

• I added an image of what the Slack notifications look like.
• I added instructions as bullet pointed lists.
• Clarified some places where I didn't know how to click into the config (mostly clicking into Configure from within Cypress).
• Added existing images for how to navigate to Org Integrations + Project Integrations.
• I updated an outdated photo/instruction in GitHub integrations also.

Let me know if any of my updates are out of line with how the Dashboard will intend to function due to any updates.

[CypressCecelia]

Should we add this to the features listed in Dashboard Introduction like we do for GitHub here?
https://docs.cypress.io/guides/dashboard/introduction.html#Integrate-with-GitHub

Additional comments on individual lines. First time doing the line suggestions, hopefully they're ok 😬

[trydionel]

This is referring to GitHub. Where did that come from?

[jennifer-shehane]

This was a mistake from copying over from GitHub doc, since we have the same steps for entering the Integrations pages.

[trydionel]

I don't love the screenshots that were added here, and the step-by-step instructions seem overly specific to the current implementation. Given that the goal of Dashboard documentation has been to focus on what's possible with a given feature, what's the rationale behind tieing the documentation so tightly to the current presentation?

[CypressCecelia]

Given that the goal of Dashboard documentation has been to focus on what's possible with a given feature what's the rationale behind tieing the documentation so tightly to the current presentation

From a support perspective, having more detailed docs should reduce the number of questions/issues that users have.

I wasn't aware that the goal of Dashboard documentation is to provide a light overview of the features (as compared to Test Runner). If this is the case, would it be possible to retain the more detailed documentation internally at least? It's helpful to know all the nuts/bolts when supporting these features.

[jennifer-shehane]

I was also not made aware of any new strategies pertaining to how the docs are written in terms of Dashboard features.

I agree with @CypressCecelia about the step by step being helpful to users we interact with.

When I review docs written for Dashboard features, I sit down and follow them to see if I can do what they say. Having never looked at Slack integration before, I got stuck at some points. Mostly where it would generically say "Configure your Slack", which was not clear where to go.

I also recognize the challenges of documenting a web application in general, where screenshots go out of date and would love to have someone full time to own our docs in order to address these issues more broadly.

[trydionel]

I'd thought we were on the same page about the goal of the Dashboard docs, apologies. Since I'm taking ownership of the Dashboard docs, I'm going to spend some time in the coming weeks on clearly defining a strategy and direction for these docs -- what we want to cover, how we can best maintain them, and how to find the balance for detailed walkthroughs vs upkeep cost. Watch for a document on that soon.

In the meantime, we can ship with the detailed walkthrough and screenshots for now. We're releasing on Tuesday, so I'd like to get this out into the wild by Monday.

[trydionel]

Actually, one tweak -- can we replace the Slack image with this? :)

[jennifer-shehane]

Update image