content: link updates for dev portal (#12901)

website/content/docs/boxes/base.mdx

@@ -58,10 +58,10 @@ boxes.
 
 Provider-specific guides for creating base boxes are linked below:
 
-- [Docker Base Boxes](/docs/docker/boxes)
-- [Hyper-V Base Boxes](/docs/hyperv/boxes)
-- [VMware Base Boxes](/docs/vmware/boxes)
-- [VirtualBox Base Boxes](/docs/virtualbox/boxes)
+- [Docker Base Boxes](/docs/providers/docker/boxes)
+- [Hyper-V Base Boxes](/docs/providers/hyperv/boxes)
+- [VMware Base Boxes](/docs/providers/vmware/boxes)
+- [VirtualBox Base Boxes](/docs/providers/virtualbox/boxes)
 
 ### Packer and Vagrant Cloud
 
@@ -282,7 +282,7 @@ provider-specific guides are linked to towards the top of this page.
 You can distribute the box file however you would like. However, if you want
 to support versioning, putting multiple providers at a single URL, pushing
 updates, analytics, and more, we recommend you add the box to
-[HashiCorp's Vagrant Cloud](/docs/vagrant-cloud).
+[HashiCorp's Vagrant Cloud](/vagrant-cloud).
 
 You can upload both public and private boxes to this service.
 

website/content/docs/boxes/format.mdx

@@ -26,7 +26,7 @@ Today, there are three different components:
   box file and so on.
 
 - Box Catalog Metadata - This is a JSON document (typically exchanged
-  during interactions with [HashiCorp's Vagrant Cloud](/docs/vagrant-cloud))
+  during interactions with [HashiCorp's Vagrant Cloud](/vagrant-cloud))
   that specifies the name of the box, a description, available
   versions, available providers, and URLs to the actual box files
   (next component) for each provider and version. If this catalog
@@ -84,7 +84,7 @@ that enables [versioning](/docs/boxes/versioning), updating, multiple
 providers from a single file, and more.
 
 -> **You do not need to manually make the metadata.** If you
-have an account with [HashiCorp's Vagrant Cloud](/docs/vagrant-cloud), you
+have an account with [HashiCorp's Vagrant Cloud](/vagrant-cloud), you
 can create boxes there, and HashiCorp's Vagrant Cloud automatically creates
 the metadata for you. The format is still documented here.
 

website/content/docs/boxes/versioning.mdx

@@ -29,7 +29,7 @@ to update your own custom boxes with versions. That is covered in
 
 `vagrant box list` only shows _installed_ versions of boxes. If you want
 to see all available versions of a box, you will have to find the box
-on [HashiCorp's Vagrant Cloud](/docs/vagrant-cloud). An easy way to find a box
+on [HashiCorp's Vagrant Cloud](/vagrant-cloud). An easy way to find a box
 is to use the url `https://vagrantcloud.com/$USER/$BOX`. For example, for
 the `hashicorp/bionic64` box, you can find information about it at
 `https://vagrantcloud.com/hashicorp/bionic64`.

website/content/docs/cli/cloud.mdx

@@ -36,7 +36,7 @@ Vagrant Cloud.
 
 **Command: `vagrant cloud auth login`**
 
-The login command is used to authenticate with [HashiCorp's Vagrant Cloud](/docs/vagrant-cloud)
+The login command is used to authenticate with [HashiCorp's Vagrant Cloud](/vagrant-cloud)
 server. Logging in is only necessary if you are accessing protected boxes.
 
 **Logging in is not a requirement to use Vagrant.** The vast majority

website/content/docs/cli/login.mdx

@@ -11,7 +11,7 @@ description: |-
 **Command: `vagrant login`**
 
 The login command is used to authenticate with the
-[HashiCorp's Vagrant Cloud](/docs/vagrant-cloud) server. Logging in is only
+[HashiCorp's Vagrant Cloud](/vagrant-cloud) server. Logging in is only
 necessary if you are accessing protected boxes or using
 [Vagrant Share](/docs/share/).
 

website/content/docs/cli/non-primary.mdx

@@ -26,8 +26,8 @@ non-primary subcommands. They're executed just like any other subcommand:
 The list of non-primary commands is below. Click on any command to learn
 more about it.
 
-- [docker-exec](/docs/docker/commands)
-- [docker-logs](/docs/docker/commands)
-- [docker-run](/docs/docker/commands)
+- [docker-exec](/docs/providers/docker/commands)
+- [docker-logs](/docs/providers/docker/commands)
+- [docker-run](/docs/providers/docker/commands)
 - [rsync](/docs/cli/rsync)
 - [rsync-auto](/docs/cli/rsync-auto)

website/content/docs/cli/plugin.mdx

@@ -104,7 +104,7 @@ This command accepts optional command-line flags:
 **Command: `vagrant plugin license <name> <license-file>`**
 
 This command installs a license for a proprietary Vagrant plugin,
-such as the [VMware Fusion provider](/docs/vmware).
+such as the [VMware Fusion provider](/docs/providers/vmware).
 
 # Plugin List
 

website/content/docs/providers/docker/index.mdx

@@ -18,7 +18,7 @@ it provides for a good workflow for developing Dockerfiles.
 ~> **Warning: Docker knowledge assumed.** We assume that
 you know what Docker is and that you are comfortable with the basics
 of Docker. If not, we recommend starting with another provider such
-as [VirtualBox](/docs/virtualbox).
+as [VirtualBox](/docs/providers/virtualbox).
 
 Use the navigation to the left to find a specific Docker topic
 to read more about.

website/content/docs/providers/vmware/vagrant-vmware-utility.mdx

@@ -37,7 +37,7 @@ generate the required certificates:
 $ sudo /opt/vagrant-vmware-desktop/bin/vagrant-vmware-utility certificate generate
 ```
 
-The path provided from this command can be used to set the [`utility_certificate_path`](/docs/vmware/configuration#utility_certificate_path) in the Vagrantfile
+The path provided from this command can be used to set the [`utility_certificate_path`](/docs/providers/vmware/configuration#utility_certificate_path) in the Vagrantfile
 configuration if installing to a non-standard path.
 
 Finally, install the service. This will also enable the service.

website/content/docs/provisioning/docker.mdx

@@ -29,7 +29,7 @@ with the Docker provisioner.
 
 -> **Note:** This documentation is for the Docker
 _provisioner_. If you are looking for the Docker _provider_, visit the
-[Docker provider documentation](/docs/docker/).
+[Docker provider documentation](/docs/providers/docker/).
 
 ## Options
 

website/content/docs/vagrantfile/machine_settings.mdx

@@ -35,13 +35,13 @@ machine that Vagrant manages.
 - `config.vm.box` (string) - This configures what [box](/docs/boxes) the
   machine will be brought up against. The value here should be the name
   of an installed box or a shorthand name of a box in
-  [HashiCorp's Vagrant Cloud](/docs/vagrant-cloud).
+  [HashiCorp's Vagrant Cloud](/vagrant-cloud).
 
 - `config.vm.box_check_update` (boolean) - If true, Vagrant will check for updates to
   the configured box on every `vagrant up`. If an update is found, Vagrant
   will tell the user. By default this is true. Updates will only be checked
   for boxes that properly support updates (boxes from
-  [HashiCorp's Vagrant Cloud](/docs/vagrant-cloud)
+  [HashiCorp's Vagrant Cloud](/vagrant-cloud)
   or some other versioned box).
 
 - `config.vm.box_download_checksum` (string) - The checksum of the box specified by
@@ -83,7 +83,7 @@ machine that Vagrant manages.
   (if specified) used only for initial HTTP request.
 
 - `config.vm.box_url` (string, array of strings) - The URL that the configured box can be found at.
-  If `config.vm.box` is a shorthand to a box in [HashiCorp's Vagrant Cloud](/docs/vagrant-cloud)
+  If `config.vm.box` is a shorthand to a box in [HashiCorp's Vagrant Cloud](/vagrant-cloud)
   then this value does not need to be specified. Otherwise, it should
   point to the proper place where the box can be found if it is not
   installed. This can also be an array of multiple URLs. The URLs will be tried in

website/content/vagrant-cloud/boxes/create.mdx

@@ -7,7 +7,7 @@ page_title: Creating a New Vagrant Box
 
 This page will cover creating a new box in Vagrant Cloud and how to distribute
 it to users. Boxes can be distributed without Vagrant Cloud, but
-miss out on several [important features](/docs/vagrant-cloud/boxes).
+miss out on several [important features](/vagrant-cloud/boxes).
 
 There are **three ways to create and upload Vagrant Boxes to Vagrant Cloud**. All
 three options are outlined below.
@@ -51,7 +51,7 @@ You can find all of your boxes in the [Vagrant section](https://vagrantcloud.com
 Once you've created and released a box, you can release new versions of
 the box by clicking "Create New Version" under the versions sidebar on
 a box page. For more information on the release lifecycle of boxes, see
-the [help page dedicated to box lifecycle](/docs/vagrant-cloud/boxes/lifecycle).
+the [help page dedicated to box lifecycle](/vagrant-cloud/boxes/lifecycle).
 
 ## Creating Boxes with the API
 

website/content/vagrant-cloud/boxes/distributing.mdx

@@ -18,7 +18,7 @@ Now when a team member runs `vagrant up`, the box will be downloaded from Vagran
 If the box is private, the team member will be prompted to authorize access. Users
 are granted access to private resources by logging in with a Vagrant Cloud username and
 password or by using a shared Vagrant Cloud token.
-[Learn more about authorization options here](/docs/vagrant-cloud/users/authentication).
+[Learn more about authorization options here](/vagrant-cloud/users/authentication).
 
 ## Private Boxes
 

website/content/vagrant-cloud/boxes/index.mdx

@@ -18,7 +18,7 @@ communicate these fixes efficiently.
 Vagrant Cloud makes it easy to manage the versioning of boxes. Versioning boxes in
 Vagrant Cloud allows for easy updates, transparent fixes, and clear communication in
 changes made. Learn more about the [box release lifecycle
-here](/docs/vagrant-cloud/boxes/lifecycle).
+here](/vagrant-cloud/boxes/lifecycle).
 
 ## Vagrant Box Catalog and Discovery
 

website/content/vagrant-cloud/boxes/release-workflow.mdx

@@ -5,7 +5,7 @@ page_title: API Release Workflow
 
 # API Release Workflow
 
-Creating new boxes through their [release lifecycle](/docs/vagrant-cloud/boxes/lifecycle)
+Creating new boxes through their [release lifecycle](/vagrant-cloud/boxes/lifecycle)
 is possible through the Vagrant Cloud website, but you can also automate
 the task via the Vagrant Cloud API.
 

website/content/vagrant-cloud/index.mdx

@@ -10,12 +10,12 @@ page_title: Vagrant Cloud
 For Vagrant Cloud questions, feedback, or feature requests, please email
 HashiCorp Support at [support+vagrantcloud@hashicorp.com](mailto:support+vagrantcloud@hashicorp.com).
 
-[Click here](/docs/vagrant-cloud/support) for more support information.
+[Click here](/vagrant-cloud/support) for more support information.
 
 ## Features
 
 Vagrant Cloud provides the following features for Vagrant:
 
-- [Vagrant Box Catalog](/docs/vagrant-cloud/boxes/catalog)
-- [Vagrant Box Creation](/docs/vagrant-cloud/boxes/create)
-- [Vagrant Box Versioning](/docs/vagrant-cloud/boxes/lifecycle)
+- [Vagrant Box Catalog](/vagrant-cloud/boxes/catalog)
+- [Vagrant Box Creation](/vagrant-cloud/boxes/create)
+- [Vagrant Box Versioning](/vagrant-cloud/boxes/lifecycle)

website/content/vagrant-cloud/organizations/authentication-policy.mdx

@@ -12,7 +12,7 @@ Enterprise.
 ## Requiring Two-Factor Authentication
 
 Organization owners can require that all organization team members use
-[two-factor authentication](/docs/vagrant-cloud/users/authentication).
+[two-factor authentication](/vagrant-cloud/users/authentication).
 Those that lack two-factor authentication will be locked out of the web
 interface until they enable it or leave the organization.
 

website/content/vagrant-cloud/support.mdx

@@ -33,7 +33,7 @@ it provides, there may be information lacking in the documentation.
 Vagrant Cloud documentation is open source.
 If you'd like to improve or correct the documentation,
 please submit a pull-request to the
-[Vagrant project on GitHub](https://github.com/hashicorp/vagrant/tree/main/website/pages/docs/vagrant-cloud/).
+[Vagrant project on GitHub](https://github.com/hashicorp/vagrant/tree/main/website/content/vagrant-cloud/).
 The Vagrant Cloud documentation can be found in the `/website/pages/vagrant-cloud/` directory.
 
 Otherwise, to make a suggestion or report an error in documentation, please

website/content/vagrant-cloud/users/index.mdx

@@ -6,5 +6,5 @@ page_title: User Accounts
 # User Accounts
 
 Users are the main identity system in Vagrant Cloud. A user can be a
-member of multiple [organizations](/docs/vagrant-cloud/organizations),
+member of multiple [organizations](/vagrant-cloud/organizations),
 as well as individually collaborate on various resources.

website/data/docs-nav-data.json

@@ -1,7 +1,7 @@
 [
   {
     "title": "Overview",
-    "path": "index"
+    "path": ""
   },
   {
     "title": "Installation",

website/data/intro-nav-data.json

@@ -1,7 +1,7 @@
 [
   {
     "title": "What is Vagrant?",
-    "path": "index"
+    "path": ""
   },
   {
     "title": "Vagrant vs. Other Software",