Request: Fix broken links and unclear content on integrations page

[zwass]

Currently the https://fleetdm.com/integrations page includes a number of broken links (mostly anchor tags). Some of the content is also unclear as it seems to suggest capabilities that are not present.

I've heard from multiple customers/community members with confusion about what these are intended to mean.

1. Okta - Broken link and I don't think we have any docs that indicate how to achieve the described "Know who opened your computer and check their device posture before you let them log into anything."
2. Active Directory- Broken link and I don't think we have any docs that indicate how to achieve the described "Know who opened your computer and check their device posture before you let them log into anything."
3. Azure - There is no guide for deploying "in minutes"
4. Ansible - The link is to a repository that shows how to deploy Fleet with Ansible, not how to integrate Fleet with Ansible. I don't think we have any docs on how to "Easily issue MDM commands and standardize data across operating systems." with Ansible
5. Chef - The link is to standard Chef documentation with nothing about Fleet integrations. I don't think we have any docs on how to "Easily issue MDM commands and standardize data across operating systems." with Chef.
6. Google Cloud - The link is to the generic deployment docs which will not help someone deploy "in minutes"
7. Munki - Links to a macOS MDM page with no mention of Munki.

Goal

User story
As a _________________________________________,
I want to _________________________________________
so that I can _________________________________________.

For help creating a user story, see "Writing a good user story" in the website handbook.

Changes

This issue's estimation includes completing the following:

• UI changes: TODO
• QA complete?

QA

The testing steps outlined below must be verified before the associated PR is merged. See "Quality" in the website handbook for help.

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

In addition to the steps above, ensure changes have been checked at all breakpoints, and a browser compatibility test has been carried out on supported browsers.

Testing notes

[fleet-release]

Links mended, meaning clear,
In cloud city, guides draw near.
Fleet's path, now sincere.

[mike-j-thomas]

Thanks for submitting this @zwass. We fixed up the broken links and took a crack at clearing up some of the unclear wording. I'll follow up in the next product marketing meeting to make sure all interaction cards are described correctly (#17022).