fix some docs links

Author: andrewjschuang

docs-v2/pages/index.mdx

@@ -25,7 +25,7 @@ To get started, [sign up for a free account](https://pipedream.com/auth/signup)
 Once you understand the basics of workflow development, learn how to get more out of Pipedream:
 
 - [Use code in workflows](/workflows/building-workflows/code/)
-- [Develop custom actions](/workflows/contributing/components/quickstart/nodejs/actions/)
+- [Develop custom actions](/workflows/contributing/components/actions-quickstart/)
 - [Develop custom triggers](/workflows/contributing/components/quickstart/nodejs/sources/)
 
 ## Use Cases

docs-v2/pages/workflows/building-workflows/actions.mdx

@@ -30,7 +30,7 @@ In your code steps with out of date actions, you'll see a button appear that wil
 
 You can author your own actions on Pipedream, too. Anytime you need to reuse the same code across steps, consider making that an action.
 
-Start with our [action development quickstart](/workflows/contributing/components/quickstart/nodejs/actions/). You can read more about all the capabilities of actions in [our API docs](/workflows/contributing/components/api/), and review [example actions here](/workflows/contributing/components/api/#example-components).
+Start with our [action development quickstart](/workflows/contributing/components/actions-quickstart/). You can read more about all the capabilities of actions in [our API docs](/workflows/contributing/components/api/), and review [example actions here](/workflows/contributing/components/api/#example-components).
 
 You can also publish actions to [the Pipedream registry](/workflows/contributing/), which makes them available for anyone on Pipedream to use.
 

docs-v2/pages/workflows/building-workflows/code/nodejs/sharing-code.mdx

@@ -9,7 +9,7 @@ Pipedream provides two ways to share code across workflows:
 
 - **Publish an action from a Node.js code step**. [Publish any Node.js code step as a reusable action](/workflows/building-workflows/code/nodejs/sharing-code/#publish-an-action-from-a-nodejs-code-step) from the Pipedream dashboard.
 
-- **Create an action from code**. Develop your action code on your local filesystem and [publish to your Pipedream account using the Pipedream CLI](/workflows/contributing/components/quickstart/nodejs/actions/).
+- **Create an action from code**. Develop your action code on your local filesystem and [publish to your Pipedream account using the Pipedream CLI](/workflows/contributing/components/actions-quickstart/).
 
 ## Publish an action from a Node.js code step
 

docs-v2/pages/workflows/building-workflows/code/python/working-with-files.mdx

@@ -111,5 +111,5 @@ To avoid errors, assume that the `/tmp` directory is empty between workflow runs
 <Callout type="warning">
 Are File Stores helpers available for Python to download, upload and manage files?
 
-At this time no, only Node.js includes a helper to interact with the [File Store](/workflows/projects/file-stores/) programmatically within workflows.
+At this time no, only Node.js includes a helper to interact with the [File Store](/workflows/data-management/file-stores/) programmatically within workflows.
 </Callout>

docs-v2/pages/workflows/building-workflows/control-flow/delay.mdx

@@ -34,7 +34,7 @@ Delayed executions can hold one of three states:
 - **Resumed**: The workflow has been resumed at the end of its delay window automatically, or resumed manually
 - **Cancelled**: The execution was cancelled manually
 
-You'll see the current state of an execution by [viewing its event data](/workflows/building-workflows/triggers/inspect/).
+You'll see the current state of an execution by [viewing its event data](/workflows/building-workflows/inspect/).
 
 #### Cancelling or resuming execution manually
 

docs-v2/pages/workflows/building-workflows/sources.mdx

@@ -143,7 +143,7 @@ Generating test data manually can result in typos or missing fields that your wo
 
 ## Publishing a new event source, or modifying an existing source
 
-Anyone can create an event source or edit an existing one. The code for all event sources is public, and kept in the [`PipedreamHQ/pipedream` repo](https://github.com/PipedreamHQ/pipedream). [Read this quickstart](/workflows/contributing/components/quickstart/nodejs/sources/) and see the [event source API docs](/workflows/contributing/components/api/) to learn more about the source development process.
+Anyone can create an event source or edit an existing one. The code for all event sources is public, and kept in the [`PipedreamHQ/pipedream` repo](https://github.com/PipedreamHQ/pipedream). [Read this quickstart](/workflows/contributing/components/sources-quickstart/) and see the [event source API docs](/workflows/contributing/components/api/) to learn more about the source development process.
 
 You can chat about source development with the Pipedream team in the `#contribute` channel of our [public Slack](https://join.slack.com/t/pipedream-users/shared_invite/zt-ernlymsn-UHfPg~Dfp08uGkAd8dpkww), and in the `#dev` topic in the [Pipedream community](https://pipedream.com/community/c/dev/11).
 

docs-v2/pages/workflows/building-workflows/triggers.mdx

@@ -717,7 +717,7 @@ If the presigned URL for the attachment has expired, then you'll need to send an
 
 If you're using email attachments in combination with [`$.flow.delay`](/workflows/building-workflows/code/nodejs/delay/) or [`$.flow.rerun`](/workflows/building-workflows/code/nodejs/rerun/) which introduces a gap of time between steps in your workflow, then there's a chance the email attachment's URL will expire.
 
-To overcome this, we suggest uploading your email attachments to your Project's [File Store](/workflows/projects/file-stores/) for persistent storage.
+To overcome this, we suggest uploading your email attachments to your Project's [File Store](/workflows/data-management/file-stores/) for persistent storage.
 
 ## RSS
 

docs-v2/pages/workflows/contributing/components/api.mdx

@@ -6,7 +6,7 @@ import Callout from '@/components/Callout'
 Our TypeScript component API is in **beta**. If you're interested in developing TypeScript components and providing feedback, [see our TypeScript docs](/workflows/contributing/components/typescript/).
 </Callout>
 
-This document was created to help developers author and use [Pipedream components](/workflows/contributing/components/). Not only can you develop [sources](/workflows/contributing/components/quickstart/nodejs/sources/) (workflow triggers) and [actions](/workflows/contributing/components/quickstart/nodejs/actions/) using the component API, but you can also develop [Node.js steps](/workflows/building-workflows/code/nodejs/) right in your workflows - without leaving your browser! You can publish components to your account for private use, or [contribute them to the Pipedream registry](/workflows/contributing/) for anyone to run.
+This document was created to help developers author and use [Pipedream components](/workflows/contributing/components/). Not only can you develop [sources](/workflows/contributing/components/sources-quickstart/) (workflow triggers) and [actions](/workflows/contributing/components/actions-quickstart/) using the component API, but you can also develop [Node.js steps](/workflows/building-workflows/code/nodejs/) right in your workflows - without leaving your browser! You can publish components to your account for private use, or [contribute them to the Pipedream registry](/workflows/contributing/) for anyone to run.
 
 While sources and actions share the same core component API, they differ in both how they're used and written, so certain parts of the component API apply only to one or the other. [This section of the docs](#differences-between-sources-and-actions) explains the core differences. When this document uses the term "component", the corresponding feature applies to both sources and actions. If a specific feature applies to only sources _or_ actions, the correct term will be used.
 
@@ -27,7 +27,7 @@ Components are Node.js modules that run on Pipedream's serverless infrastructure
 
 ### Quickstarts
 
-To help you get started, we created a step-by-step walkthrough for developing both [sources](/workflows/contributing/components/quickstart/nodejs/sources/) and [actions](/workflows/contributing/components/quickstart/nodejs/actions/). We recommend starting with those docs and using the API reference below as you develop.
+To help you get started, we created a step-by-step walkthrough for developing both [sources](/workflows/contributing/components/sources-quickstart/) and [actions](/workflows/contributing/components/actions-quickstart/). We recommend starting with those docs and using the API reference below as you develop.
 
 ### Differences between sources and actions
 
@@ -956,7 +956,7 @@ All properties from [`steps.trigger.context`](/workflows/building-workflows/trig
 
 ### Environment variables
 
-[Environment variables](/workflows/building-workflows/environment-variables/) are not accessible within sources or actions directly. Since components can be used by anyone, you cannot guarantee that a user will have a specific variable set in their environment.
+[Environment variables](/workflows/environment-variables/) are not accessible within sources or actions directly. Since components can be used by anyone, you cannot guarantee that a user will have a specific variable set in their environment.
 
 In sources, you can use [`secret` props](#props) to reference sensitive data.
 
@@ -1096,7 +1096,7 @@ You can delete a component via the UI at [https://pipedream.com/sources](https:/
 
 #### API
 
-See the [REST API docs](/workflows/building-workflows/rest-api/).
+See the [REST API docs](/rest-api/).
 
 ### Managing Actions
 

docs-v2/pages/workflows/contributing/index.mdx

@@ -12,7 +12,7 @@ the Pipedream UI when building workflows.
 What is a component?
 
 If you haven't yet, we recommend starting with our Component Development Quickstart Guides for [sources](/workflows/contributing/components/quickstart/nodejs/sources/)
-and [actions](/workflows/contributing/components/quickstart/nodejs/actions/) to learn how to build components and privately publish them to your account.
+and [actions](/workflows/contributing/components/actions-quickstart/) to learn how to build components and privately publish them to your account.
 </Callout>
 
 ## Registry Components Structure

docs-v2/pages/workflows/data-management/file-stores/index.mdx

@@ -117,7 +117,7 @@ export default defineComponent({
 })
 ```
 
-Once the file has been opened, you can [read, write, delete the file and more](/workflows/projects/file-stores/reference/).
+Once the file has been opened, you can [read, write, delete the file and more](/workflows/data-management/file-stores/reference/).
 
 ### Uploading files to File Stores