website/docs: Flesh out integrations copy changes. (#13619)

* website/docs: Flesh out integrations copy changes.

* Apply suggestions from code review

Co-authored-by: Tana M Berry <[email protected]>
Signed-off-by: Teffen Ellis <[email protected]>

* Lint.

* Revert removed section. Fix links.

* reorder integrations page sections

Signed-off-by: Fletcher Heisler <[email protected]>

* add back page title

Signed-off-by: Fletcher Heisler <[email protected]>

* move cards to very end of topic

* fix broken anchor link

---------

Signed-off-by: Teffen Ellis <[email protected]>
Signed-off-by: Fletcher Heisler <[email protected]>
Co-authored-by: Tana M Berry <[email protected]>
Co-authored-by: Fletcher Heisler <[email protected]>
Co-authored-by: Tana M Berry <[email protected]>

Author: 4 people

website/integrations/index.mdx

@@ -1,15 +1,23 @@
 ---
 title: Integrations overview
+sidebar_label: Overview
 ---
 
-There are two main types of integrations with authentik: **Applications** and **Sources**.
+## What is an integration?
 
-## Applications
+An integration is a how authentik connects to third-party applications, directories, and other identity providers.
+Integrations are categorized into two categories: **Applications** and **Sources**.
 
-authentik integrates with many applications. For a full list, and to learn more about adding documentation for a new application, refer to the [Applications](../integrations/services/index.mdx) documentation
+### Applications
 
-## Sources
+Applications include vendor tools such as Google Workspace, GitHub, Slack, or AWS. These applications can be integrated with authentik to provide single sign-on capabilities to securely authenticate users.
 
-In addition to applications, authentik also integrates with external sources, including federated directories like Active Directory and through protocols such as LDAP, OAuth, SAML, and SCIM sources. Sources are a way for authentik to use external credentials for authentication and verification. Sources in authentik can also be used for social logins, using external providers such as Facebook, Twitter, etc.
+If you want to integrate an application that isn't listed, authentik can be configured to work with most applications that support authentication protocols such as [SAML](../docs/add-secure-apps/providers/saml), [OAuth and OpenID Connect](../docs/add-secure-apps/providers/oauth2).
 
-To learn more, refer to the [Sources](https://docs.goauthentik.io/docs/users-sources/sources/index) documentation.
+To learn more, refer to the [Applications](../integrations/services) page.
+
+### Federated and social sources
+
+Sources are a way for authentik to use external user credentials for authentication. Supported integrations with external sources via authentik include federated directories like Active Directory and social logins such as Facebook, Twitter, etc. These integrations support all major protocols, including [LDAP](../docs/users-sources/sources/protocols/ldap), [SCIM](../docs/users-sources/sources/protocols/scim), [SAML](../docs/users-sources/sources/protocols/saml), and [OAuth and OpenID Connect](../docs/users-sources/sources/protocols/oauth)
+
+To learn more, refer to the [Sources](../docs/users-sources/sources) page.

website/integrations/services/index.mdx

@@ -3,27 +3,26 @@ title: Integrate with Applications
 sidebar_label: Applications
 ---
 
-# Applications
-
 import DocCardList from "@theme/DocCardList";
 import SupportBadge from "@site/src/components/SupportBadge";
 
-Below is a list of all applications that are known to work with authentik.
+# Applications
 
-:::info{title="Support Levels"}
-All app integrations will have one of these badges:
+Most third-party services that support authentication protocols such as SAML, OAuth, and OpenID Connect can be integrated with authentik, allowing users to log in to these services using their authentik credentials.
 
-|                                     |                                                            |
-| ----------------------------------- | ---------------------------------------------------------- |
-| <SupportBadge level="community" />  | The integration is community maintained.                   |
-| <SupportBadge level="vendor" />     | The integration is supported by the vendor.                |
-| <SupportBadge level="authentik" />  | The integration is regularly tested by the authentik team. |
-| <SupportBadge level="deprecated" /> | The integration is deprecated and may be removed.          |
+If you don't see an application you're looking for, let us know. You can reach us on [GitHub](https://github.com/goauthentik/authentik), [Discord](https://goauthentik.io/discord), or via email to [[email protected]](mailto:[email protected]). You can also add your own documentation for a new application integration following [these instructions](#add-a-new-application).
 
-:::
+All documented app integrations will have one of these badges:
+
+- <SupportBadge level="community" />: Community maintained.
+- <SupportBadge level="vendor" />: Supported by the vendor.
+- <SupportBadge level="authentik" />: Regularly tested by the authentik team.
+- <SupportBadge level="deprecated" />: Deprecated and may be removed.
 
 ### Add a new application
 
+<a id="add-new"></a>
+
 To add documentation for a new application (with support level Community or Vendor), please use the integration template [`service.md`](https://github.com/goauthentik/authentik/blob/main/website/integrations/template/service.md) file from our GitHub repo. You can download the template file using the following command:
 
 ```shell