Docs Restructure

docs-v2/README.md

@@ -22,7 +22,7 @@ We're moving from VuePress to Nextra. Here's what's the same and what's differen
 - New docs are here, in the `docs-v2/` directory.
 - All docs are still Markdown. Now MDX files instead of just Markdown, so extensions have been renamed to `.mdx`.
 - Keep images in `public/images/foo.png`, reference with `![alt text](/images/foo.png)`
-- Leaf nodes in VuePress were at files like `/docs/workspaces/sso/google/README.md`. Nextra allows leaf nodes to be non-index files like `/docs/workspaces/sso/google.mdx`, so there's no need for the final directory, which simplifies things.
+- Leaf nodes in VuePress were at files like `/docs/workflows/workspaces/sso/google/README.md`. Nextra allows leaf nodes to be non-index files like `/docs/workflows/workspaces/sso/google.mdx`, so there's no need for the final directory, which simplifies things.
 - VuePress used Vue, Nextra uses React. All of the custom components used in MDX files are either [built-in Nextra components](https://nextra.site/docs/guide/built-ins) or Pipedream-specific components in `components/`, ported from Vue.
 - Learn the [built-in Nextra components](https://nextra.site/docs/guide/built-ins). All the `::: tip`, `::: warning`, or other special VuePress components have an equivalent Nextra component.
 
@@ -50,8 +50,8 @@ pages
   workspaces/
     index.mdx  # /docs/workspaces
     sso/
-      index.mdx  # /docs/workspaces/sso
-      google.mdx  # /docs/workspaces/sso/google
+      index.mdx  # /docs/workflows/workspaces/sso
+      google.mdx  # /docs/workflows/workspaces/sso/google
 ```
 
 The `_meta.tsx` files in each directory defines a mapping between the labels in the sidebar and the files in that directory. If you want to add an item to the sidebar, you'll probably want to edit the `_meta.tsx` file. [See the Nextra docs](https://nextra.site/docs/docs-theme/page-configuration) for more info.

docs-v2/pages/_meta.tsx

@@ -1,30 +1,12 @@
 export default {
   "index": "What is Pipedream?",
   "quickstart": "Quickstart",
-  "workspaces": "Workspaces",
-  "projects": "Projects",
   "workflows": "Workflows",
-  "connect": {
-    title: "Connect",
-  },
-  "code": "Code",
-  "data-stores": "Data Stores",
-  "databases": "Databases",
-  "connected-accounts": "Connected Accounts",
-  "apps": "Integrations",
-  "components": "Components",
-  "sources": "Sources",
-  "event-history": "Event History",
-  "http": "HTTP",
-  "environment-variables": "Environment Variables",
-  "rest-api": "REST API",
-  "cli": "CLI",
-  "destinations": "Destinations",
-  "user-settings": "User and Billing Settings",
-  "troubleshooting": "Troubleshooting",
-  "pricing": "Pricing FAQ",
+  "connect": "Connect",
+  "pricing": "Pricing",
+  "account": "Account",
   "privacy-and-security": "Security",
-  "limits": "Limits",
+  "troubleshooting": "Troubleshooting",
   "glossary": "Glossary of Terms",
   "support": {
     title: "Support",
@@ -44,51 +26,10 @@ export default {
     href: "https://status.pipedream.com",
     newWindow: true,
   },
-  "version": {
-    title: "Version",
-    type: "menu",
-    items: {
-      v3: {
-        title: "Current",
-        href: "https://pipedream.com/docs",
-      },
-      v2: {
-        title: "Linear (classic)",
-        href: "https://pipedream.com/docs/v2",
-      },
-    },
-  },
-  "abuse": {
-    display: "hidden",
-  },
-  "airtable": {
-    display: "hidden",
-  },
-  "examples": {
-    display: "hidden",
-  },
-  "migrate-from-v1": {
-    display: "hidden",
-  },
-  "new-feature-or-bug": {
-    display: "hidden",
-  },
-  "nodejs20-faq-2024-02": {
-    display: "hidden",
-  },
-  "scheduling-future-tasks": {
-    display: "hidden",
-  },
-  "shopify-faq-2023-10": {
-    display: "hidden",
-  },
-  "subprocessors": {
-    display: "hidden",
-  },
-  "pipedream-axios": {
+  "deprecated": {
     display: "hidden",
   },
-  "status": {
+  "hidden": {
     display: "hidden",
   },
 } as const

docs-v2/pages/account/_meta.tsx

@@ -0,0 +1,4 @@
+export default {
+  "user-settings": "User Settings",
+  "billing-settings": "Billing Settings",
+} as const

docs-v2/pages/account/billing-settings.mdx

@@ -0,0 +1,43 @@
+import Callout from '@/components/Callout'
+
+# Billing Settings
+
+You'll find information on your usage data (for specific [Pipedream limits](/workflows/limits/)) in your [Billing Settings](https://pipedream.com/settings/billing). You can also upgrade to [paid plans](https://pipedream.com/pricing) from this page.
+
+## Subscription
+
+You can upgrade to [paid plans](https://pipedream.com/pricing) from this section.
+
+If you've already upgraded, you'll see an option to **Manage Subscription** here, which directs you to your personal Stripe portal. Here, you can change your payment method, review the details of previous invoices, and more.
+
+## Usage
+
+[Credits](/pricing/#credits) are Pipedream's billable unit, and users on the [free tier](/pricing/#free-tier) are limited on the number of daily free credits allocated. The **Usage** section displays a chart of the daily credits across a historical range of time to provide insight into your usage patterns.
+
+Hover over a specific column in the chart to see the number of credits run for that specific day:
+
+![Daily credits tooltip](./images/daily-invocations-tooltip.png)
+
+_Click_ on a specific column to see credits for that day, broken out by workflow / source:
+
+![Credits broken out by workflow / source](./images/usage-by-resource.png)
+
+Users on the free tier will see the last 30 days of usage in this chart. Users on [paid plans](https://pipedream.com/pricing) will see the cumulative usage tied to their current billing period.
+
+## Compute Budget
+
+Control the maximum number of compute credits permitted on your account with an _Credit Budget_.
+
+This will restrict your account-wide usage to the specified number of [credits](/pricing/#credits) on a monthly or daily basis. The compute budget does not apply to credits incurred by [dedicated workers](/workflows/visual-builder/settings/#eliminate-cold-starts).
+
+To enable this feature, _click_ on the toggle and define your maximum number of credits in the period.
+
+<Callout type="info">
+Due to how credits are accrued, there may be cases where your credit usage may _slightly_ go over the cap.
+
+In an example scenario, with cap set at 20 credits and long running workflow that uses 10 credits per run; it's possible that two concurrent events trigger the workflow, and the cap will won't apply until after the concurrent events are processed.
+</Callout>
+
+## Limits
+
+For users on the [Free tier](/pricing/#free-tier), this section displays your usage towards your [credits quota](/workflows/limits/#daily-credits-limit) for the current UTC day.

docs-v2/pages/user-settings.mdx → docs-v2/pages/account/user-settings.mdx

@@ -1,27 +1,23 @@
 import Callout from '@/components/Callout'
 import VideoPlayer from '@/components/VideoPlayer'
 
-# User and Billing Settings
+# User Settings
 
 You can find important account details, text editor configuration, and more in your [User Settings](https://pipedream.com/user).
 
-## Account
-
-You'll find your Pipedream email and other basic account details in your [Account Settings](https://pipedream.com/user).
-
-### Changing your email
+## Changing your email
 
 Pipedream sends system emails to the email address tied to your Pipedream login. You can change the email address to which these emails are delivered by modifying the **Email** in your Account Settings. Once changed, an email will be delivered to the new address requesting you verify it.
 
 Pipedream marketing emails may still be sent to the original email address you used when signing up for Pipedream. To change the email address tied to marketing emails, please [reach out to our team](https://pipedream.com/support).
 
-### Two-Factor Authentication
+## Two-Factor Authentication
 
 <VideoPlayer src="https://www.youtube.com/embed/M2_JrDh6cVI?si=1Yee9XJ10PhzoMmJ" title="Two Factor Authenitcation" />
 
 Two-factor authentication (2FA) adds an additional layer of security for your Pipedream account and is recommended for all users.
 
-#### Configuring 2FA
+### Configuring 2FA
 
 1. Open your [Account Settings](https://pipedream.com/user)
 2. Click **Configure** under **Two-Factor Authentication**
@@ -36,7 +32,7 @@ Save your recovery codes
 If you lose access to your authenticator app and your recovery codes, you will permanently lose access to your Pipedream account. **Pipedream Support cannot recover these accounts.**
 </Callout>
 
-#### Signing in with 2FA
+### Signing in with 2FA
 
 1. You'll be prompted to enter your OTP the next time you sign in to Pipedream
 2. When prompted, you can enter the OTP from your authenticator app or a recovery code
@@ -52,9 +48,9 @@ Each recovery code is a one-time-use code, so make sure to generate new recovery
 Pipedream recommends enabling 2FA with your identity provider.
 </Callout>
 
-#### Requiring 2-Factor Authentication
+### Requiring 2-Factor Authentication
 
-Workspaces on the Business plan can [require all workspace members to configure 2FA](/workspaces/#requiring-two-factor-authentication) in order to log in to Pipedream.
+Workspaces on the Business plan can [require all workspace members to configure 2FA](/workflows/workspaces/#requiring-two-factor-authentication) in order to log in to Pipedream.
 
 If you are a member of any workspace where 2FA is required, you cannot disable 2FA, but you can still reconfigure it in your [account settings](https://pipedream.com/account/) if necessary.
 
@@ -64,13 +60,13 @@ Admins and Owners control 2FA settings
 Only workspace owner and admin members can enable or disable 2FA for an entire workspace.
 </Callout>
 
-### Pipedream API Key
+## Pipedream API Key
 
-Pipedream provides a [REST API](/api/) for interacting with Pipedream programmatically. You'll find your API key here, which you use to [authorize requests to the API](/rest-api/auth/).
+Pipedream provides a [REST API](/api/) for interacting with Pipedream programmatically. You'll find your API key here, which you use to [authorize requests to the API](/workflows/rest-api/auth/).
 
 You can revoke and regenerate your API key from here at any time.
 
-### Delete Account
+## Delete Account
 
 You can delete your Pipedream account at any time by visiting your Account Settings and pressing the **Delete your Account** button. Account deletion is immediately and irreversible.
 
@@ -86,46 +82,4 @@ For example, you can:
 
 ## Environment Variables
 
-Environment variables allow you to securely store secrets or other config values that you can access in Pipedream workflows via `process.env`. [Read more about environment variables here](/environment-variables/).
-
-## Billing and Usage
-
-You'll find information on your usage data (for specific [Pipedream limits](/limits/)) in your [Billing Settings](https://pipedream.com/settings/billing). You can also upgrade to [paid plans](https://pipedream.com/pricing) from this page.
-
-### Subscription
-
-You can upgrade to [paid plans](https://pipedream.com/pricing) from this section.
-
-If you've already upgraded, you'll see an option to **Manage Subscription** here, which directs you to your personal Stripe portal. Here, you can change your payment method, review the details of previous invoices, and more.
-
-### Usage
-
-[Credits](/pricing/#credits) are Pipedream's billable unit, and users on the [free tier](/pricing/#free-tier) are limited on the number of daily free credits allocated. The **Usage** section displays a chart of the daily credits across a historical range of time to provide insight into your usage patterns.
-
-Hover over a specific column in the chart to see the number of credits run for that specific day:
-
-![Daily credits tooltip](./images/daily-invocations-tooltip.png)
-
-_Click_ on a specific column to see credits for that day, broken out by workflow / source:
-
-![Credits broken out by workflow / source](./images/usage-by-resource.png)
-
-Users on the free tier will see the last 30 days of usage in this chart. Users on [paid plans](https://pipedream.com/pricing) will see the cumulative usage tied to their current billing period.
-
-### Compute Budget
-
-Control the maximum number of compute credits permitted on your account with an _Credit Budget_.
-
-This will restrict your account-wide usage to the specified number of [credits](/pricing/#credits) on a monthly or daily basis. The compute budget does not apply to credits incurred by [dedicated workers](/workflows/settings/#eliminate-cold-starts).
-
-To enable this feature, _click_ on the toggle and define your maximum number of credits in the period.
-
-<Callout type="info">
-Due to how credits are accrued, there may be cases where your credit usage may _slightly_ go over the cap.
-
-In an example scenario, with cap set at 20 credits and long running workflow that uses 10 credits per run; it's possible that two concurrent events trigger the workflow, and the cap will won't apply until after the concurrent events are processed.
-</Callout>
-
-### Limits
-
-For users on the [Free tier](/pricing/#free-tier), this section displays your usage towards your [credits quota](/limits/#daily-credits-limit) for the current UTC day.
+Environment variables allow you to securely store secrets or other config values that you can access in Pipedream workflows via `process.env`. [Read more about environment variables here](/workflows/environment-variables/).