diff --git a/src/content/docs/Builds.md b/src/content/docs/Builds.md
deleted file mode 100644
index ab1cda0..0000000
--- a/src/content/docs/Builds.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Builds
-
-A Build is an artifact of your [Component](/docs/Components.md) Source Code that has been processed through your own [Build Steps](#build-steps).
-
-## Build Steps
-
-You can define any compilation, packaging, or testing steps for your Components within the [AppManifest](/docs/Manifests.md#appmanifest).
-
-### Run Step
-
-Execute a command.
-
-```yaml
-steps:
-  - run: npm ci
-```
-
-### Copy Step
-
-Copy files from your source code into the current directory.
-
-```yaml
-steps:
-  - copy: package.json
-  - copy: *
-```
-
-### Directory Step
-
-Set the current working directory.
-
-```yaml
-steps:
-  - directory: /build
-```
-
-## Source Code
-
-Source Code represents a discreet version of your code that has been indexed and archived by Noop.
diff --git a/src/content/docs/Environments.md b/src/content/docs/Environments.md
deleted file mode 100644
index 9398000..0000000
--- a/src/content/docs/Environments.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: 'Environments'
-description: ''
-slug: 'environments'
-section: 'core concepts'
-layout: '../../layouts/Doc.astro'
-pubDate: ''
-order: 12
----
-
-# Environments
-
-Environments are an isolated space for a single instance of an [Application](/docs/applications.md). They run on a designated Cluster and contain the [Resources](/docs/Resources.md) needed by the Application.
-
-Locally, in Noop Workshop, Environments are used exactly as they are in Cloud. Environments will each have their own database and storage resources as well as their own Secrets and Variables.
-
-An Environment can be created manually from the Application dashboard or dynamically by a Pipeline or Runbook.
-
-## Configuration using Variables and Secrets
-
-Variables and secrets can be used to configure Application runtime parameters. Variables are either defined in the Environment settings (in console) or in the Application Blueprint (app.yml).
-
-Secrets are defined exclusively in the console. Secrets are encrypted at rest and obfuscated in logs.
-
-In addition to user-defined Variables and Secrets, dynamic variables can be used to create connections between Application Components and Resources.
-
-See the [Variables and Secrets]() guide for more usage details.
-
-## Deployments
-
-The running software in an Environment is referred to as a Stack. The Stack represents a single Build Deployment. In other words the software running in an Environment relates one-to-one with a Build.
-
-A Build is the combined Variable/Secret configuration and Source Code artifact.
-
-## Previews
-
-In response to a repository event, such as a pull request, a Pipeline is able to create a temporary preview environment. The preview Environment utilizes an existing environment as the foundation to create the one-off.
-
-The preview Environment will remain online until the configured shutdown period elapses.
diff --git a/src/content/docs/environments.md b/src/content/docs/environments.md
deleted file mode 100644
index 6aeb1de..0000000
--- a/src/content/docs/environments.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: 'Environments'
-description: ''
-slug: 'environments'
-section: 'core concepts'
-layout: '../../layouts/Doc.astro'
-pubDate: ''
-order: 12
----
-
-# Environments
-
-Environments are an isolated space for a single instance of an [Application](/docs/applications.md). They run on a designated Cluster and contain the [Resources](/docs/Resources.md) needed by the Application.
-
-Locally, in Noop Workshop, Environments are used exactly as they are in Cloud. Environments will each have their own database and storage resources as well as their own Secrets and Variables.
-
-An Environment can be created manually from the Application dashboard or dynamically by a Pipeline or Runbook.
-
-## Configuration using Variables and Secrets
-
-Variables and secrets can be used to configure Application runtime parameters. Variables are either defined in the Environment settings (in console) or in the Application Blueprint (blueprint.yaml).
-
-Secrets are defined exclusively in the console. Secrets are encrypted at rest and obfuscated in logs.
-
-In addition to user-defined Variables and Secrets, dynamic variables can be used to create connections between Application Components and Resources.
-
-See the [Variables and Secrets]() guide for more usage details.
-
-## Deployments
-
-The running software in an Environment is referred to as a Stack. The Stack represents a single Build Deployment. In other words the software running in an Environment relates one-to-one with a Build.
-
-A Build is the combined Variable/Secret configuration and Source Code artifact.
-
-## Previews
-
-In response to a repository event, such as a pull request, a Pipeline is able to create a temporary preview environment. The preview Environment utilizes an existing environment as the foundation to create the one-off.
-
-The preview Environment will remain online until the configured shutdown period elapses.