Move Platform to Top Level (#1423)

* move platform to top level

* remove route from now.json

* add correct redirect

Author: Matthew Sweeney

.github/CODEOWNERS

@@ -8,14 +8,13 @@ pages/docs/v2/build-step.mdx                @leo @AndyBitz @TooTallNate @timothy
 pages/docs/v2/custom-domains.mdx            @anatrajkovska @javivelasco @mglagola @joecohens @timothyis @msweeneydev @coetry
 pages/docs/v2/serverless-functions/         @leo @AndyBitz @TooTallNate @timothyis @msweeneydev @coetry
 pages/docs/v2/network/                      @juancampa @hharnisc @dav-is @timothyis @msweeneydev @joecohens @coetry
+pages/docs/v2/platform/                     @leo @styfle @timothyis @msweeneydev @joecohens @coetry
 pages/docs/v2/advanced/now-for-github.mdx   @arunoda @timothyis @msweeneydev @coetry
 pages/docs/v2/advanced/now-for-gitlab.mdx   @arunoda @timothyis @msweeneydev @coetry
-pages/docs/configuration    @leo @styfle @AndyBitz @timothyis @msweeneydev @joecohens @coetry
+pages/docs/configuration                    @leo @styfle @AndyBitz @timothyis @msweeneydev @joecohens @coetry
 pages/docs/v2/advanced/deploy-hooks.mdx     @anatrajkovska @javivelasco @mglagola @timothyis @msweeneydev @joecohens @coetry
 pages/docs/v2/advanced/builders.mdx         @leo @AndyBitz @styfle @timothyis @msweeneydev @joecohens @coetry
-pages/docs/v2/advanced/concepts/            @leo @timothyis @msweeneydev @joecohens @coetry
 pages/docs/v2/advanced/domains/             @anatrajkovska @javivelasco @mglagola @timothyis @msweeneydev @joecohens @coetry
-pages/docs/v2/advanced/platform/            @leo @styfle @timothyis @msweeneydev @joecohens @coetry
 pages/docs/api/                             @anatrajkovska @arunoda @javivelasco @mglagola @timothyis @msweeneydev @coetry
 pages/docs/integrations/                    @arunoda @timothyis @msweeneydev @coetry
 pages/docs/error/                           @juancampa @dav-is @timothyis @msweeneydev @joecohens @coetry

components/references-mdx/api/v2/api-basics/rate-limits.mdx

@@ -32,7 +32,7 @@ status "**429 Too Many Requests**":
 
 <Note>
   You can find the complete list of rate limits in the{' '}
-  <GenericLink href="/docs/v2/advanced/platform/limits/">
+  <GenericLink href="/docs/v2/platform/limits/">
     limits documentation
   </GenericLink>
   .

components/references-mdx/configuration/configuration/configuration.mdx

@@ -22,7 +22,7 @@ export const meta = {
 
 The prefix for all new deployment instances. The CLI usually generates this field automatically based on the name of the directory. But if you'd like to define it explicitly, this is the way to go.
 
-The defined name is also used to organize the deployment into [a project](/docs/v2/advanced/platform/projects).
+The defined name is also used to organize the deployment into [a project](/docs/v2/platform/projects).
 
 <Code lang="json">{`{
   "name": "zeit-chat"
@@ -34,7 +34,7 @@ The defined name is also used to organize the deployment into [a project](/docs/
 
 **Valid values**: `1`, `2`.
 
-Specifies the [Now Platform version](/docs/v2/advanced/platform/overview#versioning) the deployment should use and is known to work with. We strongly recommend setting a `version` when working on production systems or using source control (e.g. [Git](https://git-scm.com)).
+Specifies the [Now Platform version](/docs/v2/platform/overview#versioning) the deployment should use and is known to work with. We strongly recommend setting a `version` when working on production systems or using source control (e.g. [Git](https://git-scm.com)).
 
 <Code lang="json">{`{
   "version": 2
@@ -44,7 +44,7 @@ Specifies the [Now Platform version](/docs/v2/advanced/platform/overview#version
 
 **Type**: `Array` or `String`.
 
-**Valid values**: [domain names](/docs/v2/custom-domains) (optionally including subdomains) added to the account, or a string for a suffixed URL using `.now.sh` or a [Custom Deployment Suffix](/docs/v2/advanced/platform/add-ons/#custom-deployment-suffix).
+**Valid values**: [domain names](/docs/v2/custom-domains) (optionally including subdomains) added to the account, or a string for a suffixed URL using `.now.sh` or a [Custom Deployment Suffix](/docs/v2/platform/add-ons/#custom-deployment-suffix).
 
 **Limit**: A maximum of 64 aliases in the array
 
@@ -71,7 +71,7 @@ You can deploy to the defined aliases using [Now CLI](/download) by setting the
 
 **Valid values**: For teams, either an ID or slug. For users, either a email address, username, or ID.
 
-This property determines the scope ([user or team](/docs/v2/advanced/platform/users-and-teams/)) under which the project will be deployed by [Now CLI](/download).
+This property determines the scope ([user or team](/docs/v2/platform/users-and-teams/)) under which the project will be deployed by [Now CLI](/download).
 
 Furthermore, it also affects any other actions that the user takes within the directory that contains this configuration (e.g. listing [secrets](/docs/v2/serverless-functions/env-and-secrets/) using `now secrets ls`).
 
@@ -224,7 +224,7 @@ For more information on routes, see the documentation:
 
 **Type:** `Array` of region identifier `String`.
 
-**Valid values:** a list of valid [region identifiers](/docs/v2/advanced/platform/regions-and-providers).
+**Valid values:** a list of valid [region identifiers](/docs/v2/platform/regions-and-providers).
 
 By setting and modifying this value, you can decide the deployment **regions** of the [Serverless Functions](/docs/v2/serverless-functions/introduction/) that get created as a result of the [build steps](/docs/v2/build-step). By default, the closest region to the geographical location of the deployment is used, or if using a Now for Git integration, SFO is used by default.
 
@@ -247,7 +247,7 @@ The special value `all` can be used to target all available regions.
 
 **Type**: `Boolean`.
 
-When set to `true`, both the [source view](/docs/v2/advanced/platform/deployments/#source-view) and [logs view](/docs/v2/advanced/platform/deployments/#logs-view) will be publicly accessible (when the user is authenticated with ZEIT).
+When set to `true`, both the [source view](/docs/v2/platform/deployments/#source-view) and [logs view](/docs/v2/platform/deployments/#logs-view) will be publicly accessible (when the user is authenticated with ZEIT).
 
 <Code lang="json">{`{
   "public": true

components/references-mdx/now-cli/commands/remove.mdx

@@ -34,12 +34,9 @@ The `now remove` command, which can be shortened to `now rm`, is used to remove
 
 <Note type="warning">
   By using the{' '}
-  <GenericLink href="/docs/v2/advanced/platform/projects/">
-    project name
-  </GenericLink>
-  , the entire project will be removed from the account unless the <InlineCode>
-    --safe
-  </InlineCode> is used.
+  <GenericLink href="/docs/v2/platform/projects/">project name</GenericLink>,
+  the entire project will be removed from the account unless the{' '}
+  <InlineCode>--safe</InlineCode> is used.
 </Note>
 
 ### Global Options

components/references-mdx/now-cli/commands/teams.mdx

@@ -10,7 +10,7 @@ export const meta = {
 
 ## Teams
 
-The `now teams` command is used to manage [teams](/docs/v2/advanced/platform/users-and-teams/) under an account, providing functionality to list, add, and invite new members to teams.
+The `now teams` command is used to manage [teams](/docs/v2/platform/users-and-teams/) under an account, providing functionality to list, add, and invite new members to teams.
 
 <Note type="warning">
   This command is for <b>advanced use only</b>. You can manage teams with

lib/data/guides.json

@@ -391,6 +391,6 @@
     "authors": ["msweeneydev"],
     "url": "/guides/zero-downtime-domain-migration",
     "editUrl": "pages/guides/zero-downtime-domain-migration.mdx",
-    "lastEdited": "2019-10-02T14:07:07.000Z"
+    "lastEdited": "2019-10-30T09:43:23.000Z"
   }
 ]

lib/data/v2/docs.js

@@ -41,6 +41,39 @@ export default [
       }
     ]
   },
+  {
+    name: 'Platform',
+    posts: [
+      {
+        name: 'Overview',
+        href: '/docs/v2/platform/overview'
+      },
+      {
+        name: 'Deployments',
+        href: '/docs/v2/platform/deployments'
+      },
+      {
+        name: 'Projects',
+        href: '/docs/v2/platform/projects'
+      },
+      {
+        name: 'Users and Teams',
+        href: '/docs/v2/platform/users-and-teams'
+      },
+      {
+        name: 'Limits',
+        href: '/docs/v2/platform/limits'
+      },
+      {
+        name: 'Glossary',
+        href: '/docs/v2/platform/glossary'
+      },
+      {
+        name: 'Frequently Asked Questions',
+        href: '/docs/v2/platform/frequently-asked-questions'
+      }
+    ]
+  },
   {
     name: 'Network',
     posts: [
@@ -96,39 +129,6 @@ export default [
       {
         name: 'Deploy Hooks',
         href: '/docs/v2/advanced/deploy-hooks'
-      },
-      {
-        name: 'Platform',
-        posts: [
-          {
-            name: 'Overview',
-            href: '/docs/v2/advanced/platform/overview'
-          },
-          {
-            name: 'Deployments',
-            href: '/docs/v2/advanced/platform/deployments'
-          },
-          {
-            name: 'Projects',
-            href: '/docs/v2/advanced/platform/projects'
-          },
-          {
-            name: 'Users and Teams',
-            href: '/docs/v2/advanced/platform/users-and-teams'
-          },
-          {
-            name: 'Limits',
-            href: '/docs/v2/advanced/platform/limits'
-          },
-          {
-            name: 'Glossary',
-            href: '/docs/v2/advanced/platform/glossary'
-          },
-          {
-            name: 'Frequently Asked Questions',
-            href: '/docs/v2/advanced/platform/frequently-asked-questions'
-          }
-        ]
       }
     ]
   }

now.json

@@ -226,9 +226,9 @@
       "headers": { "Location": "/docs/configuration#global" }
     },
     {
-      "src": "/docs/v2/platform/(.*)/?",
+      "src": "/docs/v2/advanced/platform/(.*)/?",
       "status": 301,
-      "headers": { "Location": "/docs/v2/advanced/platform/$1" }
+      "headers": { "Location": "/docs/v2/platform/$1" }
     },
     {
       "src": "/docs/v2/development/basic/(.*)/?",
@@ -253,14 +253,7 @@
       "src": "/docs/version-detection",
       "status": 301,
       "headers": {
-        "Location": "/docs/v2/advanced/platform/frequently-asked-questions#platform-version-detection"
-      }
-    },
-    {
-      "src": "/docs/v2/advanced/concepts/lambdas(.*)",
-      "status": 301,
-      "headers": {
-        "Location": "/docs/v2/advanced/concepts/serverless-functions$1"
+        "Location": "/docs/v2/platform/frequently-asked-questions#platform-version-detection"
       }
     }
   ]

pages/docs/error/application/BODY_NOT_A_STRING_FROM_FUNCTION.mdx

@@ -6,7 +6,7 @@ export const meta = {
   title: 'Body Not A String From Serverless Function',
   description: 'The Serverless Function did not respond with a string.',
   editUrl: 'pages/docs/error/application/BODY_NOT_A_STRING_FROM_FUNCTION.mdx',
-  lastEdited: '2019-10-22T21:47:59.000Z'
+  lastEdited: '2019-10-30T09:43:23.000Z'
 }
 
 #### Application Error
@@ -27,7 +27,7 @@ This is an error with the application.
 
 #### Troubleshoot
 
-- Check the application logs, which can be found at the host URL under [the `/_logs` path](/docs/v2/advanced/platform/deployments/#logs-view), for example:
+- Check the application logs, which can be found at the host URL under [the `/_logs` path](/docs/v2/platform/deployments/#logs-view), for example:
   ```
   https://my-deployment-lwbxweoqjo.now.sh/_logs
   ```

pages/docs/error/application/FUNCTION_INVOCATION_TIMEOUT.mdx

@@ -7,7 +7,7 @@ export const meta = {
   description:
     'The requested Serverless Function reached the request timeout threshold.',
   editUrl: 'pages/docs/error/application/FUNCTION_INVOCATION_TIMEOUT.mdx',
-  lastEdited: '2019-10-22T21:47:59.000Z'
+  lastEdited: '2019-10-30T09:43:23.000Z'
 }
 
 #### Application Error
@@ -26,7 +26,7 @@ The request for a Serverless Function reached the timeout threshold (5 minutes f
 
 #### Troubleshoot
 
-- A common cause for this issue is when the application contains an unhandled exception. Check the application logs, which can be found at the host URL under [the `/_logs` path](/docs/v2/advanced/platform/deployments/#logs-view), for example:
+- A common cause for this issue is when the application contains an unhandled exception. Check the application logs, which can be found at the host URL under [the `/_logs` path](/docs/v2/platform/deployments/#logs-view), for example:
   ```
   https://my-deployment-lwbxweoqjo.now.sh/_logs
   ```

pages/docs/error/application/NO_STATUS_CODE_FROM_FUNCTION.mdx

@@ -7,7 +7,7 @@ export const meta = {
   description:
     'The requested Serverless Function failed to respond with a status code.',
   editUrl: 'pages/docs/error/application/NO_STATUS_CODE_FROM_FUNCTION.mdx',
-  lastEdited: '2019-10-22T21:47:59.000Z'
+  lastEdited: '2019-10-30T09:43:23.000Z'
 }
 
 #### Application Error
@@ -27,7 +27,7 @@ The application did not respond with a status code.
 #### Troubleshoot
 
 - Make sure the Serverless Function from the application responds with a status code.
-- Check the application logs, which can be found at the host URL under [the `/_logs` path](/docs/v2/advanced/platform/deployments/#logs-view), for example:
+- Check the application logs, which can be found at the host URL under [the `/_logs` path](/docs/v2/platform/deployments/#logs-view), for example:
   ```
   https://my-deployment-lwbxweoqjo.now.sh/_logs
   ```

pages/docs/v2/advanced/now-for-gitlab.mdx

@@ -9,7 +9,7 @@ export const meta = {
   description:
     'Deploy each change in your GitLab projects with ZEIT Now to share and test with your colleagues. Instant share-able links to your work with each push. Automatically make your changes available from production domains.',
   editUrl: 'pages/docs/v2/advanced/now-for-gitlab.mdx',
-  lastEdited: '2019-10-10T22:30:47.000Z'
+  lastEdited: '2019-10-30T09:43:23.000Z'
 }
 
 The Now for GitLab integration automatically deploys your GitLab projects with [ZEIT Now](/now), providing staging URLs and automatic production domain updates.
@@ -31,7 +31,7 @@ Now for GitLab provides:
 
 ### Step 1: Link ZEIT Now to Your GitLab Account
 
-You can connect your Now account to GitLab by visiting your [account or team](/docs/v2/advanced/platform/users-and-teams) [settings page](/account) and clicking the "Connect with GitLab" button.
+You can connect your Now account to GitLab by visiting your [account or team](/docs/v2/platform/users-and-teams) [settings page](/account) and clicking the "Connect with GitLab" button.
 
 <Image
 src={`${process.env.ASSETS}/docs/now-for-gitlab/connect-with-gitlab.png`}

pages/docs/v2/build-step.mdx

@@ -156,7 +156,7 @@ If you change the value of a [Now Secret](#adding-secrets) or environment variab
 
 ### Reserved Variables
 
-The ZEIT Now platform reserves the usage of some environment variable names by default. You can find a list of these names in the [limits documentation](/docs/v2/advanced/platform/limits/#reserved-variables).
+The ZEIT Now platform reserves the usage of some environment variable names by default. You can find a list of these names in the [limits documentation](/docs/v2/platform/limits/#reserved-variables).
 
 ## Ignored Files and Folders
 

pages/docs/v2/environment-variables-and-secrets.mdx

@@ -9,7 +9,7 @@ export const meta = {
   description:
     'Creating and using environment variables and creating and using secret environment variables in your ZEIT Now deployments',
   editUrl: 'pages/docs/v2/environment-variables-and-secrets.mdx',
-  lastEdited: '2019-10-22T21:51:28.000Z'
+  lastEdited: '2019-10-30T09:43:23.000Z'
 }
 
 If there's information or certain behavior of your project that needs to differ depending on if it's running locally or on ZEIT Now, environment variables offer the perfect solution.
@@ -105,7 +105,7 @@ The syntax required to make the environment variable available inside the build
 
 ### Built-In Variables
 
-By default, all deployments expose the `NOW_REGION` environment variable to [Serverless Functions](/docs/v2/serverless-functions/introduction/) which provides the [region](/docs/v2/advanced/platform/regions-and-providers/) that the lambda was deployed to.
+By default, all deployments expose the `NOW_REGION` environment variable to [Serverless Functions](/docs/v2/serverless-functions/introduction/) which provides the [region](/docs/v2/platform/regions-and-providers/) that the lambda was deployed to.
 
 ### Reserved Variables
 

pages/docs/v2/network/headers.mdx

@@ -6,7 +6,7 @@ export const meta = {
   title: 'Headers',
   description: 'The list of headers included with deployments with ZEIT Now.',
   editUrl: 'pages/docs/v2/network/headers.mdx',
-  lastEdited: '2019-10-22T21:51:28.000Z'
+  lastEdited: '2019-10-30T09:43:23.000Z'
 }
 
 [HTTP headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers) can be found in both the HTTP Request and HTTP Response.
@@ -41,7 +41,7 @@ This header represents the unique deployment, not the staging or production doma
 
 ### `x-now-trace`
 
-Contains a list of [regions](/docs/v2/advanced/platform/regions-and-providers/) through which the request has traversed, usually the region closest to the visitor.
+Contains a list of [regions](/docs/v2/platform/regions-and-providers/) through which the request has traversed, usually the region closest to the visitor.
 
 <Note>
   The trace is where a request was processed, it is not necessarily where a
@@ -106,7 +106,7 @@ The unique identifier for each request.
 
 ### `x-now-trace`
 
-Contains a list of [regions](/docs/v2/advanced/platform/regions-and-providers/) through which the request has traversed, usually the region center closest to you.
+Contains a list of [regions](/docs/v2/platform/regions-and-providers/) through which the request has traversed, usually the region center closest to you.
 
 <Note>
   The trace is where a request was processed, it is not necessarily where a