Split out connector documentation into individual sections

[alexfrancoeur]

Our docs look great for alerts and actions (thanks @peterschretlen!). I'm opening this issue to split out connectors into their own individual sections. As this library grows, we'll probably need that regardless. But as we begin to work with some of these companies, it'll be easier for us to link out to integrations in our documentation if they're separate sections. It also allows us to go into a little more detail with screenshots, etc.

https://www.elastic.co/guide/en/kibana/7.x/action-types.html

cc: @gchaps @arisonl

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[gchaps]

Separating the connectors into individual sections would be equivalent to how connectors are documented in the Elasticsearch docs. It would also leave room to provide some examples.

[peterschretlen]

++ what's there is minimal, it would be great to build on it by separating out each action and showing screenshots of both connector and action UIs (the current page combines the parameters for both, which can be somewhat confusing).

[alexfrancoeur]

Something similar that might help for inspiration, workplace search content sources: https://www.elastic.co/guide/en/workplace-search/current/workplace-search-content-sources.html

While focusing on one integration initially, we'll need to provide more detailed documentation for each connector shortly after. @arisonl and I can help with this

[alexfrancoeur]

Just to be proactive, is there any way we can share the URL structure ahead of time? Would be it a simple deep link or do we need a hierarchy?

https://www.elastic.co/guide/en/kibana/current/[action name].html or
https://www.elastic.co/guide/en/kibana/current/action-types/[action name].html

[mikecote]

@alexfrancoeur working on this locally, what I have so far is the following:

• http://localhost:8000/guide/action-types.html
• http://localhost:8000/guide/email-action-type.html
• http://localhost:8000/guide/index-action-type.html
• http://localhost:8000/guide/pagerduty-action-type.html
• http://localhost:8000/guide/server-log-action-type.html
• http://localhost:8000/guide/slack-action-type.html
• http://localhost:8000/guide/webhook-action-type.html

So it would be the former I believe.

[alexfrancoeur]

Great, thanks Mike! I'll move forward with this assumption, let me know if anything changes

[mikecote]

@alexfrancoeur @arisonl the documentation is now live with the split:

• https://www.elastic.co/guide/en/kibana/7.7/action-types.html
• https://www.elastic.co/guide/en/kibana/7.7/pagerduty-action-type.html