broken links wip

Author: davemooreuws

docs/get-started/foundations/deployment/index.mdx

@@ -10,9 +10,9 @@ You can read about why this separation is important on the [why nitric](/get-sta
 
 <Note>
   If you're new to Nitric we recommend starting with the [quickstart
-  guide](/guides/quickstart) to get a feel for how Nitric works. You can return
-  to this page later to learn more about the deployment process and how to
-  customize it.
+  guide](/get-started/quickstart) to get a feel for how Nitric works. You can
+  return to this page later to learn more about the deployment process and how
+  to customize it.
 </Note>
 
 ## Provider Types

docs/get-started/foundations/infrastructure/index.mdx

@@ -4,7 +4,7 @@ description: Nitric allows applications to declare infrastructure requirements a
 
 # Infrastructure
 
-If you haven't read [Why Nitric](/get-started/get-started/foundations/why-nitric) yet, you might want to start there. It explains the 'why' behind Nitric, which can help you understand the 'what' and 'how' of Nitric.
+If you haven't read [Why Nitric](/get-started/foundations/why-nitric) yet, you might want to start there. It explains the 'why' behind Nitric, which can help you understand the 'what' and 'how' of Nitric.
 
 Nitric applies the concept of Infrastructure from Code (IfC) in a very specific way, to enhance Infrastructure as Code (IaC) and help applications with platform specific Separation of Concerns (SoC).
 

docs/get-started/foundations/infrastructure/resources.mdx

@@ -6,7 +6,7 @@ description: An overview of cloud resources provided by the Nitric framework
 
 Nitric provides cloud-native building blocks that make it simple to declare the resources you need as part of your application code.
 
-The Nitric deployment engine will run through your code at deployment time, collecting a graph of all the required resources and their interactions. This information is forwarded to a [Nitric plugin](/foundations/deployment#providers) during deployment, which provisions the resources in the cloud.
+The Nitric deployment engine will run through your code at deployment time, collecting a graph of all the required resources and their interactions. This information is forwarded to a [Nitric plugin](/get-started/foundations/deployment#providers) during deployment, which provisions the resources in the cloud.
 
 During development though, you can interact with these resources as if they were local objects, making it easy to build and test your application. Here we'll discuss the different types of resources you can declare in Nitric, and some best practices for working with them.
 

docs/get-started/foundations/projects/configuration.mdx

@@ -39,7 +39,7 @@ The name of your project. This is used to identify your project and it used when
 
 ### `services`
 
-A list of [service](/foundations/infrastructure/services) types that make up your project. Typically, nitric will build each service in your project into a separate container image. Each service can have its own runtime, build configuration, and start command.
+A list of [service](/get-started/foundations/infrastructure/services) types that make up your project. Typically, nitric will build each service in your project into a separate container image. Each service can have its own runtime, build configuration, and start command.
 
 #### `match`
 
@@ -95,7 +95,7 @@ If a runtime is provided it must match the name of a runtime configuration in th
 
 Type is essentially the name for this group of services. It is used to group services together for deployment and resource management. If not provided, the service will be grouped under the 'default' type.
 
-The most common use case for this is grouping service with similar deployed resource requirements together. For example, you make have a set of services that required additional vCPU or memory resources at runtime. You can group these services together under a specific type and apply resource constraints to that type in a [stack file](/foundations/deployment/stacks).
+The most common use case for this is grouping service with similar deployed resource requirements together. For example, you make have a set of services that required additional vCPU or memory resources at runtime. You can group these services together under a specific type and apply resource constraints to that type in a [stack file](/get-started/foundations/deployment/stacks).
 
 For example, if you have a set of services that require additional memory, you can group them together under a type named `memory-intensive`, separate from the default type.
 
@@ -144,9 +144,9 @@ go run ./services/service2/main.go
 
 ### `batch-services` (optional)
 
-A list of [batch service](/foundations/infrastructure/services#batch-services) types that make up your project. Batch services are used to run high-performance computing tasks, data processing or tasks requiring GPUs, or a large number of vCPUs or memory.
+A list of [batch service](/get-started/foundations/infrastructure/services#batch-services) types that make up your project. Batch services are used to run high-performance computing tasks, data processing or tasks requiring GPUs, or a large number of vCPUs or memory.
 
-Batch services are similar to services but are optimized for running batch processing tasks. You can read more about batch services in the [batch service](/foundations/infrastructure/services#batch-services) section.
+Batch services are similar to services but are optimized for running batch processing tasks. You can read more about batch services in the [batch service](/get-started/foundations/infrastructure/services#batch-services) section.
 
 The configuration options for `batch-services` are the same as for `services`.
 

docs/get-started/quickstart.mdx

@@ -238,7 +238,7 @@ After your service is running, it will register itself with the server. All the
 
 The output will also show the local dashboard URL, the dashboard will automatically refresh with API details and other useful tools for building your application.
 
-Once the API is registered, you can test the API using any HTTP client, your browser, or the [local dashboard](/get-started/local-dashboard):
+Once the API is registered, you can test the API using any HTTP client, your browser, or the [local dashboard](/get-started/foundations/projects/local-development):
 
 ```bash
 curl http://localhost:4001/hello/John
@@ -447,4 +447,4 @@ nitric down
 
 - Learn more about [APIs](/apis)
 - See other features in the [introduction](/#building-blocks)
-- Learn more about the [foundations](/foundations/projects) of Nitric
+- Learn more about the [foundations](/get-started/foundations/projects) of Nitric

docs/providers/index.mdx

@@ -41,7 +41,7 @@ It also significantly reduces the burden of writing project specific Infrastruct
 
 ![Nitric Architecture](/docs/images/guides/custom-provider/custom-provider-architecture.png)
 
-You can find out more about how the Nitric CLI and SDK interact with providers on the [deployment](/foundations/deployment) section.
+You can find out more about how the Nitric CLI and SDK interact with providers on the [deployment](/get-started/foundations/deployment) section.
 
 ## Standard Providers
 

docs/providers/pulumi/aws/imports.mdx

@@ -8,7 +8,7 @@ Nitric allows you to import existing AWS resources into your Nitric project. Cur
 
 ## How imports work
 
-If you have existing AWS resources that you would like to use in your Nitric project, you may be able to import them using the `import` section of your Nitric [stack file](/foundations/deployment/stacks). This section allows you to import existing resources and use them in your Nitric project. This indicates to the `nitric/aws` provider that you would like to use the existing resources in your Nitric project, rather than create a new one.
+If you have existing AWS resources that you would like to use in your Nitric project, you may be able to import them using the `import` section of your Nitric [stack file](/get-started/foundations/deployment/stacks). This section allows you to import existing resources and use them in your Nitric project. This indicates to the `nitric/aws` provider that you would like to use the existing resources in your Nitric project, rather than create a new one.
 
 Imports are stack specific, meaning that you can import resources into a specific stack file, and they will only be available in that stack. Other stacks for the same project can either create or import those resources as needed.
 

docs/reference/cli.mdx

@@ -103,7 +103,7 @@ When you are ready to test your application and you want to run it locally, you
 nitric start
 ```
 
-This will run the Nitric server for local testing. This will output local endpoints for your apis and open the [local dashboard](/get-started/local-dashboard) for testing.
+This will run the Nitric server for local testing. This will output local endpoints for your apis and open the [local dashboard](/get-started/foundations/projects/local-development) for testing.
 
 For more information on local development, see the [local development](/reference/cli/local-development) docs.
 

docs/reference/csharp/v0/collection/collection.mdx

@@ -33,7 +33,7 @@ Nitric.Run();
 
 ## Access
 
-All Nitric resources provide access permissions you can use to specify the level of access your code needs to the resource. See here for details about infrastructure [security](/foundations/infrastructure/security).
+All Nitric resources provide access permissions you can use to specify the level of access your code needs to the resource. See here for details about infrastructure [security](/get-started/foundations/infrastructure/security).
 
 ### Available permissions:
 

docs/reference/csharp/v0/queues/queue.mdx

@@ -31,7 +31,7 @@ Nitric.Run();
 
 ## Access
 
-All Nitric resources provide access permissions you can use to specify the level of access your code needs to the resource. See here for details about infrastructure [security](/foundations/infrastructure/security).
+All Nitric resources provide access permissions you can use to specify the level of access your code needs to the resource. See here for details about infrastructure [security](/get-started/foundations/infrastructure/security).
 
 ### Available permissions: