docs: using base directory again

Author: JessicaSachs

src/.vuepress/config.js

@@ -4,58 +4,58 @@ const sidebar = {
       title: 'Essentials',
       collapsable: false,
       children: [
-        '/v2/guide/installation',
-        '/v2/guide/introduction',
-        '/v2/guide/a-crash-course',
-        '/v2/guide/conditional-rendering',
-        '/v2/guide/event-handling',
-        '/v2/guide/passing-data',
-        '/v2/guide/forms'
+        '/guide/installation',
+        '/guide/introduction',
+        '/a-crash-course',
+        '/conditional-rendering',
+        '/event-handling',
+        '/passing-data',
+        '/forms'
       ]
     },
     {
       title: 'Vue Test Utils in depth',
       collapsable: false,
       children: [
-        '/v2/guide/slots',
-        '/v2/guide/async-suspense',
-        '/v2/guide/http-requests',
-        '/v2/guide/transitions',
-        '/v2/guide/component-instance',
-        '/v2/guide/reusability-composition',
-        '/v2/guide/vuex',
-        '/v2/guide/vue-router',
-        '/v2/guide/third-party',
-        '/v2/guide/stubs-shallow-mount'
+        '/slots',
+        '/async-suspense',
+        '/http-requests',
+        '/transitions',
+        '/component-instance',
+        '/reusability-composition',
+        '/vuex',
+        '/vue-router',
+        '/third-party',
+        '/stubs-shallow-mount'
       ]
     },
     {
       title: 'Extending Vue Test Utils',
       collapsable: false,
-      children: ['/v2/guide/plugins', '/v2/guide/community-learning']
+      children: ['/plugins', '/community-learning']
     },
     {
       title: 'Migration to Vue Test Utils 2',
       collapsable: false,
-      children: ['/v2/guide/migration']
+      children: ['/migration']
     },
     {
       title: 'API Reference',
       collapsable: false,
-      children: ['/v2/api/']
+      children: ['/api/']
     }
   ],
   api: [
     {
       title: 'API Reference',
       collapsable: false,
-      children: ['/v2/api/']
+      children: ['/api/']
     }
   ]
 }
 
 module.exports = {
-  base: '/',
+  base: '/v2/',
   title: 'Vue Test Utils',
   locales: {
     '/': {
@@ -67,13 +67,13 @@ module.exports = {
     editLinks: true,
     sidebarDepth: 2,
     sidebar: {
-      '/v2/guide/': sidebar.guide,
-      '/v2/api/': sidebar.api
+      '/': sidebar.guide,
+      '/api/': sidebar.api
     },
     nav: [
-      { text: 'Guide', link: '/v2/guide/introduction' },
-      { text: 'API Reference', link: '/v2/api/' },
-      { text: 'Migration from VTU 1', link: '/v2/guide/migration' },
+      { text: 'Guide', link: '/introduction' },
+      { text: 'API Reference', link: '/api/' },
+      { text: 'Migration from VTU 1', link: '/migration' },
       { text: 'GitHub', link: 'https://github.com/vuejs/vue-test-utils-next' }
     ]
   }

src/v2/api/README.md renamed to src/api/README.md

@@ -6,7 +6,7 @@ You might know Vue updates reactively; when you change a value, the DOM is autom
 
 ## A Simple Example - Updating with `trigger`
 
-Let's re-use the `<Counter>` component from [event handling](/v2/guide/event-handling) with one change; we now render the `count` in the `template`.
+Let's re-use the `<Counter>` component from [event handling]./event-handling) with one change; we now render the `count` in the `template`.
 
 ```js
 const Counter = {
@@ -104,7 +104,7 @@ test('uses a mocked axios HTTP client and flush-promises', async () => {
 
 ```
 
-> If you haven't tested Components with API requests before, you can learn more in [HTTP Requests](/v2/guide/http-requests).
+> If you haven't tested Components with API requests before, you can learn more in [HTTP Requests]./http-requests).
 ## Conclusion
 
 - Vue updates the DOM asynchronously; tests runner execute code synchronously.

src/v2/guide/a-crash-course.md renamed to src/guide/a-crash-course.md

@@ -63,11 +63,11 @@ test('does not render an admin link', () => {
 })
 ```
 
-Notice we are calling `exists()` on the value returned from `.find()`? `find()`, like `mount()`, also returns a wrapper, similar to `mount()`. `mount()` has a few extra methods, because it's wrapping a Vue component, and `find()` only returns a regular DOM node, but many of the methods are shared between both. Some other methods include `classes()`, which gets the classes a DOM node has, and `trigger()` for simulating user interaction. You can find a list of methods supported [here](/v2/api/#wrapper-methods).
+Notice we are calling `exists()` on the value returned from `.find()`? `find()`, like `mount()`, also returns a wrapper, similar to `mount()`. `mount()` has a few extra methods, because it's wrapping a Vue component, and `find()` only returns a regular DOM node, but many of the methods are shared between both. Some other methods include `classes()`, which gets the classes a DOM node has, and `trigger()` for simulating user interaction. You can find a list of methods supported [here](.,/api/#wrapper-methods).
 
 ## Using `data`
 
-The final test is to assert that the admin link is rendered when `admin` is `true`. It's `false` by default, but we can override that using the second argument to `mount()`, the [`mounting options`](/v2/api/#mount-options).
+The final test is to assert that the admin link is rendered when `admin` is `true`. It's `false` by default, but we can override that using the second argument to `mount()`, the [`mounting options`](.,/api/#mount-options).
 
 For `data`, we use the aptly named `data` option:
 
@@ -89,7 +89,7 @@ test('renders an admin link', () => {
 
 If you have other properties in `data`, don't worry - Vue Test Utils will merge the two together. The `data` in the mounting options will take priority over any default values.
 
-To learn what other mounting options exist, see [`Passing Data`](/v2/guide/passing-data.html) or see [`mounting options`](/v2/api/#mount-options).
+To learn what other mounting options exist, see [`Passing Data`]./passing-data.html) or see [`mounting options`](.,/api/#mount-options).
 
 ## Conclusion
 

src/v2/guide/async-suspense.md renamed to src/guide/async-suspense.md

@@ -40,7 +40,7 @@ test('emits an event when clicked', () => {
 })
 ```
 
-> If you haven't seen `trigger()` before, don't worry. It's used to simulate user interaction. You can learn more in [Forms](/v2/guide/forms).
+> If you haven't seen `trigger()` before, don't worry. It's used to simulate user interaction. You can learn more in [Forms]./forms).
 
 The first thing to notice is that `emitted()` returns an object, where each key matches an emitted event. In this case, `increment`.
 

src/v2/guide/community-learning.md renamed to src/guide/community-learning.md

@@ -78,7 +78,7 @@ test('trigger', async () => {
 })
 ```
 
-> If you haven't seen `emitted()` before, don't worry. It's used to assert the emitted events of a Component. You can learn more in [Event Handling](/v2/guide/event-handling).
+> If you haven't seen `emitted()` before, don't worry. It's used to assert the emitted events of a Component. You can learn more in [Event Handling]./event-handling).
 
 We trigger the `click` event listener, so that the Component executes the `submit` method. As we did with `setValue`, we use `await` to make sure the action is being reflected by Vue.
 
@@ -228,7 +228,7 @@ We then make a simple assertion, whether the form emitted the correct event and
 
 #### Native form submission
 
-Triggering a `submit` event on a `<form>` element mimics browser behavior during form submission. If we wanted to trigger form submission more naturally, we could trigger a `click` event on the submit button instead. Since form elements not connected to the `document` cannot be submitted, as per the [HTML specification](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-submission-algorithm), we need to use [`attachTo`](/v2/api/#attachto) to connect the wrapper's element.
+Triggering a `submit` event on a `<form>` element mimics browser behavior during form submission. If we wanted to trigger form submission more naturally, we could trigger a `click` event on the submit button instead. Since form elements not connected to the `document` cannot be submitted, as per the [HTML specification](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#form-submission-algorithm), we need to use [`attachTo`](.,/api/#attachto) to connect the wrapper's element.
 
 #### Multiple modifiers on the same event
 

src/v2/guide/component-instance.md renamed to src/guide/component-instance.md

@@ -38,11 +38,11 @@ test('displays message', () => {
 
 ## What Next?
 
-To see Vue Test Utils in action, [take the Crash Course](/v2/guide/a-crash-course/), where we build a simple Todo app using a test-first approach.
+To see Vue Test Utils in action, [take the Crash Course]./a-crash-course/), where we build a simple Todo app using a test-first approach.
 
 Docs are split into two main sections:
 
 * **Essentials**, to cover common uses cases you'll face when testing Vue components.
 * **Vue Test Utils in Depth**, to explore other advanced features of the library.
 
-Alternatively, you can explore the full [API](/v2/api/).
+Alternatively, you can explore the full [API](.,/api/).

src/v2/guide/conditional-rendering.md renamed to src/guide/conditional-rendering.md

@@ -74,7 +74,7 @@ test('renders an error if length is too short', () => {
 })
 ```
 
-Writing a test for a `maxLength` rule is left as an exercise for the reader! Another way to write this would be using `setValue` to update the input with a password that is too short. You can learn more in [Forms](/v2/guide/forms). 
+Writing a test for a `maxLength` rule is left as an exercise for the reader! Another way to write this would be using `setValue` to update the input with a password that is too short. You can learn more in [Forms]./forms). 
 
 ## Using `setProps`