[DO NOT MERGE] Contentful Launch, Attempt 2 (#9285)

Co-authored-by: Tami Goodall <[email protected]>
Co-authored-by: erjohnson <[email protected]>
Co-authored-by: Rachel Khoriander <[email protected]>
Co-authored-by: David <[email protected]>

Author: 5 people

articles/api/authentication/legacy/_impersonation.md

@@ -79,8 +79,3 @@ Use this endpoint to obtain an impersonation URL to login as another user. Usefu
 - To distinguish between real logins and impersonation logins, the profile of the impersonated user will contain additional impersonated and impersonator properties. For example: `"impersonated": true, "impersonator": {"user_id": "auth0|...", "email": "[email protected]"}`.
 
 - For a regular web app, you should set the `additionalParameters`: set the `response_type` to be `code`, the `callback_url` to be the <dfn data-key="callback">callback URL</dfn> to which Auth0 will redirect with the authorization code, and the <dfn data-key="scope">`scope`</dfn> to be the JWT claims that you want included in the JWT.
-
-
-### More Information
-
-- [Impersonate Users](/users/guides/impersonate-users-using-the-dashboard)

articles/architecture-scenarios/implementation/b2b/b2b-architecture.md

@@ -25,7 +25,7 @@ In most cases, provisioning separate Auth0 tenants for your customer's organizat
 * Your customers' organizations have isolated users that aren't shared with other organizations.
 * You have some customer organizations that support more than one IdP. For example, your customer has their own IdP but also has some users that aren't in their IdP and whose credentials you will need to store. Or, your customer wants to provide for one or more social connections in addition to their enterprise IdP.
 
-If both of these situations are the case, then we recommend that you create separate Auth0 tenants for each customer that needs it. This allows you to have a separate custom domain for them and to easily customize their login experience, including [Home Realm Discovery](/architecture-scenarios/b2b/b2b-authentication#home-real-discovery) on their login page.
+If both of these situations are the case, then we recommend that you create separate Auth0 tenants for each customer that needs it. This allows you to have a separate custom domain for them and to easily customize their login experience, including [Home Realm Discovery](/architecture-scenarios/implementation/b2b/b2b-authentication#home-real-discovery) on their login page.
 
 ::: warning
 Maintaining multiple Auth0 tenants can add complexity to your system and should not be done unless absolutely necessary.

articles/architecture-scenarios/implementation/b2b/b2b-provisioning.md

@@ -46,7 +46,7 @@ You need to provision those users at the IdP level. Each of the organizations wi
     * You convince them to create (or find that they already have) one master IdP that can route to their individual IdPs.
     * You create separate organizations (e.g. customerorg-department1 and customerorg-department2) in your applications.
     * You set up a new Auth0 tenant just for them and add as many IdPs as they need (which may include a database in Auth0) to that tenant, along with their own custom domain and branding.
-    * You make your existing tenant and login page more complex to handle [Home Realm Discovery](/architecture-scenarios/b2b/b2b-authentication#home-real-discovery) just for organizations that have more than one IdP.
+    * You make your existing tenant and login page more complex to handle [Home Realm Discovery](/architecture-scenarios/implementation/b2b/b2b-authentication#home-real-discovery) just for organizations that have more than one IdP.
 
 We recommend using Auth0 as an IdP as a starting point because it’s simple to implement a user invite workflow: an administrator creates a user; a randomly-generated password is created for that user, but never stored or shown to anyone; and then the user receives a welcome email with a link to set their password. Compared to other invite flows, the only thing special about this is that the person who is creating the user will have to either select the organization ahead of time, or the system will force the organization to match that of the user doing the inviting (in situations where there is an organization administrator who belongs to that organization only). To learn more, see [User invite](#user-invite).
 

articles/architecture-scenarios/web-app-sso/part-2.md

@@ -85,7 +85,7 @@ For more information on database connections refer to [Database Identity Provide
 
 ### Create an Active Directory / LDAP Connection
 
-Next you need to configure your Active Directory / LDAP connection. Go to the [Auth0 dashboard](${manage_url}) and in the side navigation select the [Connections > Enterprise](${manage_url}/#/connections/enterprise)).
+Next you need to configure your Active Directory / LDAP connection. Go to the [Auth0 dashboard](${manage_url}) and in the side navigation, select [Connections > Enterprise](${manage_url}/#/connections/enterprise).
 
 There you need to create the AD / LDAP connection and install the AD Connector. You can find details in these documents:
 - [How to connect your Active Directory with Auth0](/connections/enterprise/active-directory-ldap)

articles/connections/calling-an-external-idp-api.md

@@ -49,7 +49,7 @@ You will need an Access Token to call the [Management API](/api/management/v2).
 
 If this is the first time you are requesting a [Management APIv2 Token](/api/management/v2/tokens), you will need to create and configure an application that can be used to call the Management API:
 
-1. From the [registered Auth0 Management API](${manage_url}/#/apis/management/authorized-clients) in the [Dashboard], click the **API Explorer** tab.
+1. From the [registered Auth0 Management API](${manage_url}/#/apis/management/authorized-clients) in the [Dashboard](${manage_url}), click the **API Explorer** tab.
 
 2. Click **Create & Authorize a Test Application**.
 

articles/connections/database/custom-db/index.md

@@ -37,6 +37,5 @@ Whatever the use case, Auth0 extensibility allows you to tailor IdAM operations
   'connections/database/custom-db/overview-custom-db-connections',
   'connections/database/custom-db/create-db-connection',
   'connections/database/custom-db/templates',
-  'best-practices/custom-db-connections',
   'connections/database/custom-db/error-handling'
 ] }) %>

articles/integrations/azure-api-management/configure-auth0.md

@@ -70,7 +70,7 @@ Once Auth0 has created your Connection, you'll be redirected to your Connection'
 
 Finally, we'll create a user that we use later on to test the integration.
 
-Go to the [Users section]((${manage_url}/#/users)) of the Management Dashboard. Click **Create User**.
+Go to the [Users section](${manage_url}/#/users) of the Management Dashboard. Click **Create User**.
 
 ![](/media/articles/integrations/azure-api-mgmt/auth0/user.png)
 

articles/libraries/lock/v11/index.md

@@ -77,7 +77,7 @@ Make sure you read about the [limitations of cross-origin authentication](/cross
 
 ### 1. Initializing Lock
 
-First, you'll need to initialize a new `Auth0Lock` object, and provide it with your Auth0 client ID (the unique client ID for each Auth0 application, which you can get from the [management dashboard](${manage_url})) and your Auth0 domain (for example `yourname.auth0.com`).
+First, you'll need to initialize a new `Auth0Lock` object, and provide it with your Auth0 client ID (the unique client ID for each Auth0 application, which you can get from the [management dashboard](${manage_url})) and your Auth0 domain (for example, `yourname.auth0.com`).
 
 ```js
 // Initializing our Auth0Lock

articles/users/search/v2/query-syntax.md

@@ -38,7 +38,7 @@ You can search for users using the following fields:
   - `family_name`
 
 ::: warning
-New tenants, starting September 1st 2017, cannot search any of the `app_metadata` fields. Paid tenants (that is, tenants that have a credit card associated in the [Dashboard](${manage_url}/#/tenant/billing/payment)), that were created up to August 31st 2017, can search using the `app_metadata` fields.
+New tenants, starting September 1st 2017, cannot search any of the `app_metadata` fields. Paid tenants (that is, tenants that have a credit card associated in the [Dashboard](${manage_url}/#/tenant/billing/payment)) that were created up to August 31st 2017, can search using the `app_metadata` fields.
 Note that [Search v3](/users/search/v3/query-syntax) does not have this restriction.
 :::
 For more information, see the [Metadata Overview](/users/concepts/overview-user-metadata).

config/cards.yml

@@ -9,17 +9,17 @@
   icon: "icon-budicon-499"
   color: "orange"
   description: "Learn the basics of using Auth0."
-  url: "/getting-started"
+  url: "/get-started"
   articles:
 
     - title: "Create a Tenant"
-      url: "/getting-started/create-tenant"
+      url: "/get-started/learn-the-basics"
 
     - title: "Set Up An App"
-      url: "/getting-started/set-up-app"
+      url: "/get-started/learn-the-basics"
 
     - title: "Add Login"
-      url: "/application-auth/current"
+      url: "/authorization/authentication-and-authorization"
 
 - id: "ui-components"
   title: "Login"
@@ -68,7 +68,7 @@
       url: "/authorization"
 
     - title: "Role-based Access Control"
-      url: "/authorization/concepts/rbac"
+      url: "/authorization/rbac"
 
     - title: "Authorization Extension"
       url: /extensions/authorization-extension
@@ -85,10 +85,10 @@
       url: "/users"
 
     - title: "User Profiles"
-      url: "/users/concepts/overview-user-profile"
+      url: "/users/user-profiles"
 
     - title: "Import & Export Users"
-      url: "/users/concepts/overview-user-migration"
+      url: "/users/import-and-export-users"
 
 - id: "apis"
   title: "APIs"
@@ -99,7 +99,7 @@
   articles:
 
     - title: "API Overview"
-      url: "/api/info"
+      url: "/api"
 
     - title: "Authentication API"
       url: "/api/authentication"
@@ -119,13 +119,13 @@
   articles:
 
     - title: "Introduction to Identity"
-      url: "/videos/learn-identity/01-introduction-to-identity"
+      url: "/videos/learn-identity-series/learn-identity-series/introduction-to-identity"
 
     - title: "OpenID Connect and OAuth2"
-      url: "/videos/learn-identity/02-oidc-and-oauth"
+      url: "/videos/learn-identity-series/openid-connect-and-oauth2"
 
     - title: "Web Sign-In"
-      url: "/videos/learn-identity/03-web-sign-in"
+      url: "/videos/learn-identity-series/web-sign-in"
 
 - id: "extensibility"
   title: "Extensibility"
@@ -136,7 +136,7 @@
   articles:
 
     - title: "Rules"
-      url: "/rules/current"
+      url: "/rules"
 
     - title: "Extensions"
       url: "/extensions"
@@ -149,14 +149,14 @@
   icon: "icon-budicon-399"
   color: "green"
   description: "Guides and tutorials on working with Auth0."
-  url: "/topics/guides"
+  url: "/architecture-scenarios"
   articles:
 
-    - title: "Architecture Scenarios"
-      url: /architecture-scenarios
+    - title: "Private Cloud"
+      url: "/private-cloud"
 
     - title: "Monitoring"
-      url: "/monitoring"
+      url: "/monitor-auth0"
 
     - title: "Deployments"
       url: "/deploy"

config/included-folders.yml

@@ -0,0 +1,9 @@
+- /articles/architecture-scenarios
+- /articles/api/authentication
+- /articles/api/authorization-extension
+- /articles/connections
+- /articles/microsites
+- /articles/quickstart
+- /articles/_includes
+- /snippets
+- /updates