Make breadcrumbs clickable (#1492)

* add individual pages

* half of new pages

* rest

* remove docs clickable

* remove next-env

* tweaks

Author: tiffanyqi

Diff for: next-env.d.ts

@@ -2,4 +2,4 @@
 /// <reference types="next/image-types/global" />
 
 // NOTE: This file should not be edited
-// see https://nextjs.org/docs/basic-features/typescript for more information.
+// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information.

Diff for: package-lock.json

@@ -57,7 +57,7 @@ Here’s a quick summary of changes:
     </iframe>
 </div>
 
-Insights, Funnels and Retention now all follow the same structure. In the query builder on the left, you can define the behavior you want to measure, as well as the way to measure it. Each query builder now has its own self contained definition of a [metric](/docs/reports/overview#metrics). We’ll be leveraging this concept more in the future. More chart types are available across funnels and retention, allowing you to visualize funnel and retention metrics in more way than before.
+Insights, Funnels and Retention now all follow the same structure. In the query builder on the left, you can define the behavior you want to measure, as well as the way to measure it. Each query builder now has its own self contained definition of a [metric](/docs/reports#metrics). We’ll be leveraging this concept more in the future. More chart types are available across funnels and retention, allowing you to visualize funnel and retention metrics in more way than before.
 
 ### See Revenue Drop off in Funnels
 

Diff for: pages/changelogs/2024-02-13-new-funnels-retention.mdx

@@ -17,6 +17,6 @@ video: "https://www.loom.com/embed/e84c62b2454d496b960fb0fdb09b9785"
 
 You can now save a funnel or retention behavior definition, and reuse it across your reports. This allows you standardize on a definition and feel confident in not missing any changes if you need to update a definition. This also saves time from not having to redefine your funnel or retention behavior for every report.
 
-Note that the [behavior](/docs/reports/overview#behaviors) is saved, and not the [metric](/docs/reports/overview#metrics), so you can use the same funnel to in your conversion rate metric, as well as your time to convert metric.
+Note that the [behavior](/docs/reports#behaviors) is saved, and not the [metric](/docs/reports#metrics), so you can use the same funnel to in your conversion rate metric, as well as your time to convert metric.
 
 You can save and share your behavior definitions just like a custom event or custom property. You'll be able to see all saved behaviors in Lexicon. See [docs](/docs/features/saved-behaviors) for more information on saved behaviors.

Diff for: pages/changelogs/2024-04-03-save-funnel-retention-behaviors.mdx

@@ -0,0 +1,11 @@
+import { Card, Cards } from 'nextra/components'
+
+# Access Security
+
+Mixpanel is committed to keeping your data and access secure.
+
+<Cards>
+  <Card icon title="Login Methods" href="/docs/access-security/login-methods" />
+  <Card icon title="Two-Factor Authentication" href="/docs/access-security/two-factor-authentication" />
+  <Card icon title="Single Sign-On" href="/docs/access-security/single-sign-on" />
+</Cards>

Diff for: pages/docs/access-security.mdx

@@ -37,7 +37,7 @@ Additional access security requirements may be configured across an Organization
 
 **Single Sign-On**: Enable users of your organization to log in with single sign-on. Can also require users to login using SSO and assign roles/permissions via IdP.
 
-Read more about Two-Factor Authentication [here](/docs/access-security/two-factor-authentication) and Single Sign-On [here](/docs/access-security/single-sign-on/overview).
+Read more about Two-Factor Authentication [here](/docs/access-security/two-factor-authentication) and Single Sign-On [here](/docs/access-security/single-sign-on).
 
 
 ## FAQ

Diff for: pages/docs/access-security/login-methods.mdx

@@ -1,5 +1,4 @@
 {
-    "overview": "Overview",
     "azure": "Azure",
     "jumpcloud": "JumpCloud",
     "okta": "Okta",

Diff for: pages/docs/access-security/single-sign-on/overview.mdx renamed to pages/docs/access-security/single-sign-on.mdx

@@ -3,7 +3,7 @@
 
 ## Overview
 
-Before using this document, read the [general Mixpanel SSO set-up instructions](/docs/access-security/single-sign-on/overview).
+Before using this document, read the [general Mixpanel SSO set-up instructions](/docs/access-security/single-sign-on).
 
 You have two setup options in order to use Single Sign-On (SSO) for Mixpanel through Okta:
 
@@ -13,7 +13,7 @@ B.  If you have a more custom setup, follow Okta's documentation on setting up a
 
 ### Configure SSO in Mixpanel
 
-Follow the [general SSO set-up instructions](/docs/access-security/single-sign-on/overview).
+Follow the [general SSO set-up instructions](/docs/access-security/single-sign-on).
 
 Make sure to collect your postback URL and successfully claim your domain.
 

Diff for: pages/docs/access-security/single-sign-on/_meta.json

@@ -16,7 +16,7 @@ This feature is available to customers on an Enterprise Plan.
 
 ## Admin Organizations
 
-An Admin Organization is a special type of Organization that contains Single Sign-On settings and Claimed Domains. It can have Organization Members, but you should only add administrative users to the Admin Organization to manage security. The [SCIM](/docs/access-security/single-sign-on/overview#scim) process will add Users as Organization Members.
+An Admin Organization is a special type of Organization that contains Single Sign-On settings and Claimed Domains. It can have Organization Members, but you should only add administrative users to the Admin Organization to manage security. The [SCIM](/docs/access-security/single-sign-on#scim) process will add Users as Organization Members.
 
 An "Admin" Organization is different from a regular Organization in that it will not have Projects, Teams, a Plan or Billing, or Service Accounts. Other than administrators (those with Admin or Owner roles), any Organization Members will not see the Admin Organization or interact with it directly.
 
@@ -30,7 +30,7 @@ Any Organization linked to an Admin Organization will use the Single Sign-On set
 
 SSO settings and Claimed Domains are managed in the Admin Organization. Administrative users who manage SSO settings in the Admin Organization do not need to be members of the Linked Organization(s), and vice-versa.
 
-This configuration supports [SCIM](/docs/access-security/single-sign-on/overview#scim).
+This configuration supports [SCIM](/docs/access-security/single-sign-on#scim).
 
 ## Differences From Single-Organization SSO
 
@@ -51,7 +51,7 @@ SCIM|IDP Groups = Mixpanel Teams|IDP Groups = Mixpanel Linked Organizations*
 ## Setting Up Shared SSO
 
 <Callout type="warning">
-    If you already use Azure for SSO with Mixpanel, you must [remove existing SSO configuration](/docs/access-security/single-sign-on/overview#remove-sso-configuration) before migrating, due to constraints with “Issuer URL” and “Identifier (Entity ID).” Contact Mixpanel by [opening a Mixpanel support ticket](https://mixpanel.com/get-support).
+    If you already use Azure for SSO with Mixpanel, you must [remove existing SSO configuration](/docs/access-security/single-sign-on#remove-sso-configuration) before migrating, due to constraints with “Issuer URL” and “Identifier (Entity ID).” Contact Mixpanel by [opening a Mixpanel support ticket](https://mixpanel.com/get-support).
 </Callout>
 
 ### 1. Create an Admin Organization in Mixpanel
@@ -65,9 +65,9 @@ For an existing Organization in Mixpanel, go to Organization Settings > Access S
 The new Admin Organization will be listed in the left nav in Organization Settings.
 ![SSO Admin Organization Navigation Image](/sso_admin_org_nav.png)
 
-### 2. [Set up SSO](/docs/access-security/single-sign-on/overview) for the Admin Organization
+### 2. [Set up SSO](/docs/access-security/single-sign-on) for the Admin Organization
 
-Follow the steps to set up SSO in the Admin Organization as you would for a regular Organization. [SSO documentation](/docs/access-security/single-sign-on/overview).
+Follow the steps to set up SSO in the Admin Organization as you would for a regular Organization. [SSO documentation](/docs/access-security/single-sign-on).
 
 ### 3. Link any Organizations to the Admin Organization in Mixpanel
 
@@ -91,7 +91,7 @@ Once your organizations are linked, you can then transfer any domains you might
 
 ![SSO Domain Transfer Image](/sso_domain_transfer_image.png)
 
-### 5. (Optional) Set up [SCIM](/docs/access-security/single-sign-on/overview#scim)
+### 5. (Optional) Set up [SCIM](/docs/access-security/single-sign-on#scim)
 
 The configurable "SCIM Name" for the Linked Organization must match a group in your IDP. Members of the matching group will be added to the Linked Organization.
 
@@ -120,7 +120,7 @@ If you have Single Sign-On configured for an Organization, and want to use the s
 Be sure to follow these steps in this order, or there will be more downtime for Single Sign-On.
 
 1. In Mixpanel, [Create an Admin Organization](#1-create-an-admin-organization-in-mixpanel)
-2. In Mixpanel, Set up SSO for the Admin Organization and configure an application in your IDP with the corresponding settings. You can refer to the [Single Sign-on Overview section](/docs/access-security/single-sign-on/overview) in our docs or to the respective IDP docs for [Azure](/docs/access-security/single-sign-on/azure) or [Okta](/docs/access-security/single-sign-on/okta)
+2. In Mixpanel, Set up SSO for the Admin Organization and configure an application in your IDP with the corresponding settings. You can refer to the [Single Sign-on Overview section](/docs/access-security/single-sign-on) in our docs or to the respective IDP docs for [Azure](/docs/access-security/single-sign-on/azure) or [Okta](/docs/access-security/single-sign-on/okta)
 3. In your IDP, assign all users (who will be using Mixpanel in any Linked Organization) into the newly configured app
 4. (Optional) In your IDP, set up SCIM for the newly configured app, but **do not start pushing groups**
 5. In Mixpanel, transfer claimed Domains from the original Organization to the Admin Organization. Any claimed Domains in a Linked Organization will be hidden when the Organizations are linked (step 6).

Diff for: pages/docs/access-security/single-sign-on/okta.md

@@ -1,5 +1,4 @@
 {
-    "overview": "Overview",
     "templates": "Templates",
     "boards-on-boards": "Boards on Boards",
     "public-boards": "Public Boards",

Diff for: pages/docs/access-security/single-sign-on/shared-sso.mdx

@@ -1,6 +1,5 @@
 {
-    "overview": "Overview",
     "webhooks": "Webhooks",
     "build-an-integration": "Build an Integration",
-    "integrations": "Integrations┇"
+    "integrations": "Integrations"
 }

Diff for: pages/docs/boards/overview.mdx renamed to pages/docs/boards.mdx

@@ -33,7 +33,7 @@ _It is not recommended to use the same tag name for two static exports, as users
 **For dynamically syncing exports:** Every 15 minutes, Mixpanel will initiate a sync between the Mixpanel cohort and the Airship tag. At the time of the sync, Mixpanel will add the tag for newly-qualified users, and remove the tag for users who have exited the cohort. Users can move into and out of the cohort depending on if they meet the cohort criteria. Note that these tags only apply to the “mixpanel” Tag Group Key, which must be created within Airship.
 
 ## How are users matched between Airship and Mixpanel?
-> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management/identity-management#identity-merge-apis) must have the $user_id in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
+> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management#identity-merge-apis) must have the $user_id in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
 
 Users are matched between Airship and Mixpanel using the [Airship channel id](https://docs.airship.com/guides/airship/user-guide/channels-intro/#channel-ids). This value must be set as a Mixpanel user property named `$ios_urban_airship_channel_id` for iOS users or `$android_urban_airship_channel_id` for Android users. These values must match with the Airship channel id.
 

Diff for: pages/docs/boards/_meta.json

@@ -31,7 +31,7 @@ Follow these steps to enable the integration with Apptimize:
 
 ## Matching Users between Apptimize and Mixpanel
 
-> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management/identity-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarly applicable to projects on the original ID merge system.
+> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarly applicable to projects on the original ID merge system.
 
 Mixpanel only exports identified user profiles (users with at least 1 set profile properties) to match to Apptimize - users without user profiles (i.e. anonymous users) will not export.
 

Diff for: pages/docs/cohort-sync/overview.md renamed to pages/docs/cohort-sync.md

@@ -91,7 +91,7 @@ In order to build a Braze Segment after importing a cohort:
 
 ## Matching Mixpanel and Braze Users
 
-> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management/identity-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
+> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
 
 In order to match Mixpanel users to ones on Braze's end, the user in Mixpanel should have a profile property named $braze_external_id with the value you have assigned in Braze to the same user as [external_user_id](https://www.braze.com/docs/developer_guide/platform_integration_guides/ios/analytics/setting_user_ids/#suggested-user-id-naming-convention).
 

Diff for: pages/docs/cohort-sync/_meta.json

@@ -24,7 +24,7 @@ To enable the integration with CleverTap:
 
 3. Specify a **Connector Name** and enter the CleverTap **Project ID**, **Passcode**, and **Data center** details to authorize the connection.
 
-4. You can optionally select the user properties to export by clicking on the ***Edit Columns*** and selecting the user properties you wish to be included in the export. The default user properties that are exported can be found [here](/docs/cohort-sync/overview#limits).
+4. You can optionally select the user properties to export by clicking on the ***Edit Columns*** and selecting the user properties you wish to be included in the export. The default user properties that are exported can be found [here](/docs/cohort-sync#limits).
 
 5. The CleverTap integration will show a **Connected** tag in the UI once the connection establishes.
 

Diff for: pages/docs/cohort-sync/integrations/airship.md

@@ -55,7 +55,7 @@ The Mixpanel Cohort is available in the Audience list. Mixpanel exports cohort d
 
 ## Matching Users between Mixpanel and Iterable
 
-> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management/identity-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
+> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
 
 The best way to match users from Mixpanel to Iterable is to set the `$iterable_user_id` profile property with the user's Iterable User ID. This also prevents Iterable from overwriting the Iterable User ID with the Mixpanel Distinct ID upon cohort sync from Mixpanel.
 

Diff for: pages/docs/cohort-sync/integrations/apptimize.md

@@ -32,7 +32,7 @@ The Leanplum integration will show a **Connected** tag in the UI once the connec
 
 ## Matching Users Between Leanplum and Mixpanel
 
-> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management/identity-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
+> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
 
 Mixpanel only exports identified user profiles to match to Leanplum - users without user profile properties (i.e. anonymous users) will not export.
 

Diff for: pages/docs/cohort-sync/integrations/braze.md

@@ -29,7 +29,7 @@ You will need to provide an API key (referred to as an Authorization token in Ma
 
 ## Matching Users between Mailchimp and Mixpanel
 
-> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management/identity-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
+> **Warning:** Projects using the [simplified ID merge system](/docs/tracking-methods/id-management#identity-merge-apis) must have the `$user_id` in Mixpanel match the user identifier in the partner service. Using any alternative partner properties to match users between tools may result in partner events not being attributed to the correct user in Mixpanel. Any partner properties mentioned in the below section are primarily applicable to projects on the original ID merge system.
 
 Mixpanel only exports identified user profiles to match to Mailchimp - users without user profile properties (i.e. anonymous users) will not export.