website/docs: new landing page for Providers

website/docs/outposts/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: Overview
+title: Outposts
 ---
 
 An outpost is a single deployment of an authentik component, which can be deployed in a completely separate environment:
@@ -15,7 +15,7 @@ Upon creation, a service account and a token is generated. The service account o
 
 authentik can manage the deployment, updating and general lifecycle of an Outpost. To communicate with the underlying platforms on which the outpost is deployed, authentik has several built-in integrations.
 
--   If you've deployed authentik on docker-compose, authentik automatically creates an integration for the local docker socket (See [Docker](./integrations/docker.md)).
+-   If you've deployed authentik on Docker Compose, authentik automatically creates an integration for the local docker socket (See [Docker](./integrations/docker.md)).
 -   If you've deployed authentik on Kubernetes, with `kubernetesIntegration` set to true (default), authentik automatically creates an integrations for the local Kubernetes Cluster (See [Kubernetes](./integrations/kubernetes.md)).
 
 To deploy an outpost with these integrations, simply select them during the creation of an Outpost. A background task is started, which creates the container/deployment. You can see that Status on the System Tasks page.

website/docs/policies/index.md

@@ -1,5 +1,5 @@
 ---
-title: Overview
+title: Policies
 ---
 
 ## Event-matcher policy

website/docs/providers/index.md

@@ -0,0 +1,22 @@
+---
+title: Providers
+slug: /providers
+---
+
+A Provider is an authentication method, a service that is used by authentik to authenticate the user for the associated application. Common Providers are OpenID Connect (OIDC)/OAuth2, LDAP, SAML, and generic proxy provider, and others.
+
+Providers are the "other half" of [applications](../applications/index.md). They typically exist in a 1-to-1 relationship; each application needs a provider and every provider can be used with one application.
+
+You can create a new provider in the Admin interface, or you can use the [Application wizard](../applications/manage_apps.md#instructions) to create a new application and its provider at the same time.
+
+Refer to the documentation for each provider:
+
+-   [LDAP](./ldap/index.md)
+-   [OAuth2/OpenID](./oauth2/index.md)
+-   [Proxy provider](./proxy/index.md)
+-   [RAC (Remote Access Control)](./rac/index.md)
+-   [Radius](./radius/index.md)
+-   [SAML](./saml/index.md)
+-   [SCIM](./scim/index.md)
+
+You can also create a SAML provider by uploading an SP metadata XML file that contains the service provider's configuration data. SAML metadata is used to share configuration information between the Identity Provider (IdP) and the Service Provider (SP). An SP metadata XML file typically contains the SP certificate, the entity ID, the Assertion Consumer Service URL (ACS URL), and a log out URL (SingleLogoutService).

website/sidebars.js

@@ -68,6 +68,10 @@ const docsSidebar = {
         {
             type: "category",
             label: "Providers",
+            link: {
+                type: "doc",
+                id: "providers/index",
+            },
             items: [
                 {
                     type: "category",