diff --git a/docs/config.md b/docs/config.md
index 5177ef4..60c12a3 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -40,7 +40,7 @@ config:
 
 ## Choosing a PHP version
 
-You can set `php` to any version that is available in our [php service](https://docs.lando.dev/php/).
+You can set `php` to any version that is available in our [php service](https://docs.lando.dev/plugins/php/).
 
 However, you should consult the [Drupal requirements](https://www.drupal.org/docs/getting-started/system-requirements) to make sure that the version of `php` you choose is actually supported by the version of `drupal` you are running.
 
@@ -54,7 +54,7 @@ config:
 
 ## Choosing a composer version
 
-You can set `composer_version` to any version that is available in our [php service](https://docs.lando.dev/php/config.html#installing-composer).
+You can set `composer_version` to any version that is available in our [php service](https://docs.lando.dev/plugins/php/config.html#installing-composer).
 
 ```yaml
 recipe: drupal9
@@ -64,7 +64,7 @@ config:
 
 ## Choosing a webserver
 
-By default this recipe will be served by the default version of our [apache](https://docs.lando.dev/apache) service but you can also switch this to use [`nginx`](https://docs.lando.dev/nginx). We *highly recommend* you check out both the [apache](https://docs.lando.dev/apache) and [nginx](https://docs.lando.dev/nginx) services before you change the default `via`.
+By default this recipe will be served by the default version of our [apache](https://docs.lando.dev/plugins/apache) service but you can also switch this to use [`nginx`](https://docs.lando.dev/plugins/nginx). We *highly recommend* you check out both the [apache](https://docs.lando.dev/plugins/apache) and [nginx](https://docs.lando.dev/plugins/nginx) services before you change the default `via`.
 
 #### With Apache (default)
 
@@ -84,9 +84,9 @@ config:
 
 ## Choosing a database backend
 
-By default this recipe will use the default version of our [mysql](https://docs.lando.dev/mysql) service as the database backend but you can also switch this to use [`mariadb`](https://docs.lando.dev/mariadb) or [`postgres`](https://docs.lando.dev/postgres) instead. Note that you can also specify a version *as long as it is a version available for use with lando* for either `mysql`, `mariadb` or `postgres`.
+By default this recipe will use the default version of our [mysql](https://docs.lando.dev/plugins/mysql) service as the database backend but you can also switch this to use [`mariadb`](https://docs.lando.dev/plugins/mariadb) or [`postgres`](https://docs.lando.dev/plugins/postgres) instead. Note that you can also specify a version *as long as it is a version available for use with lando* for either `mysql`, `mariadb` or `postgres`.
 
-If you are unsure about how to configure the `database` we *highly recommend* you check out the [`mysql`](https://docs.lando.dev/mysql), [`mariadb`](https://docs.lando.dev/mariadb) and [`postgres`](https://docs.lando.dev/postgres) services before you change the default.
+If you are unsure about how to configure the `database` we *highly recommend* you check out the [`mysql`](https://docs.lando.dev/plugins/mysql), [`mariadb`](https://docs.lando.dev/plugins/mariadb) and [`postgres`](https://docs.lando.dev/plugins/postgres) services before you change the default.
 
 Also note that like the configuration of the `php` version you should consult the [Drupal requirements](https://www.drupal.org/docs/getting-started/system-requirements) to make sure the `database` and `version` you select is actually supported by the version of Drupal you are using.
 
@@ -148,7 +148,7 @@ You may need to override our [default Drupal config](https://github.com/lando/dr
 
 If you do this you must use files that exist inside your application and express them relative to your project root as below.
 
-Note that the default files may change based on how you set both `ssl` and `via`. Also note that the `vhosts` and `server` config will be either for `apache` or `nginx` depending on how you set `via`. We *highly recommend* you check out both the [apache](https://docs.lando.dev/apache/config.html) and [nginx](https://docs.lando.dev/nginx/config.html) if you plan to use a custom `vhosts` or `server` config.
+Note that the default files may change based on how you set both `ssl` and `via`. Also note that the `vhosts` and `server` config will be either for `apache` or `nginx` depending on how you set `via`. We *highly recommend* you check out both the [apache](https://docs.lando.dev/plugins/apache/config.html) and [nginx](https://docs.lando.dev/plugins/nginx/config.html) if you plan to use a custom `vhosts` or `server` config.
 
 **A hypothetical project**
 
diff --git a/docs/legacy/drupal-7.md b/docs/legacy/drupal-7.md
index c9c58c7..3b94643 100644
--- a/docs/legacy/drupal-7.md
+++ b/docs/legacy/drupal-7.md
@@ -77,7 +77,7 @@ config:
 
 While Lando will globally install Drush for you it is increasingly common and in some cases a straight-up best practice to [install a site-local Drush](https://www.drush.org/latest/install/) by requiring it in your projects `composer.json` file.
 
-Because of how Lando's [php service](https://docs.lando.dev/php) sets up its [`PATH`](https://docs.lando.dev/php/caveats.html) this means that if you have indeed installed Drush on your own via `composer` Lando will use yours over its own.
+Because of how Lando's [php service](https://docs.lando.dev/plugins/php) sets up its [`PATH`](https://docs.lando.dev/plugins/php/caveats.html) this means that if you have indeed installed Drush on your own via `composer` Lando will use yours over its own.
 
 Said more explicitly: **if you've required `drush` via `composer` in your application then this recipe will use your `drush` and not the one you've specified in this recipes config.**
 
diff --git a/docs/tooling.md b/docs/tooling.md
index ec5b427..fc2ac9d 100644
--- a/docs/tooling.md
+++ b/docs/tooling.md
@@ -96,7 +96,7 @@ tooling:
 
 ## Using xdebug
 
-This is just a passthrough option to the [xdebug setting](https://docs.lando.dev/php/config.html#using-xdebug) that exists on all our [php services](https://docs.lando.dev/php). The `tl;dr` is `xdebug: true` enables and configures the php xdebug extension and `xdebug: false` disables it.
+This is just a passthrough option to the [xdebug setting](https://docs.lando.dev/plugins/php/config.html#using-xdebug) that exists on all our [php services](https://docs.lando.dev/plugins/php). The `tl;dr` is `xdebug: true` enables and configures the php xdebug extension and `xdebug: false` disables it.
 
 ```yaml
 recipe: drupal9
@@ -104,7 +104,7 @@ config:
   xdebug: true|false
 ```
 
-However, for more information we recommend you consult the [php service documentation](https://docs.lando.dev/php).
+However, for more information we recommend you consult the [php service documentation](https://docs.lando.dev/plugins/php).
 
 
 ## Importing Your Database
diff --git a/netlify.toml b/netlify.toml
index 5842233..96d6003 100644
--- a/netlify.toml
+++ b/netlify.toml
@@ -39,13 +39,13 @@
 # We need this so preview environments and the base site look ok on their own
 [[redirects]]
   from = "/"
-  to = "/drupal"
+  to = "/plugins/drupal"
   status = 200
 [[redirects]]
-  from = "/drupal/*"
+  from = "/plugins/drupal/*"
   to = "/:splat"
   status = 200
 [[redirects]]
-  from = "/drupal/legacy-versions.html"
-  to = "/drupal/legacy/drupal-8.html"
+  from = "/plugins/drupal/legacy-versions.html"
+  to = "/plugins/drupal/legacy/plugins/drupal-8.html"
   status = 200