fix dead links

Author: yyx990803

src/.vitepress/config.ts

@@ -259,12 +259,12 @@ export const sidebar = {
         }
         // {
         //   text: 'Building a Library for Vue',
-        //   link: '/guide/advanced/building-a-library'
+        //   link: '/guide/extras/building-a-library'
         // },
-        // { text: 'Custom Renderers', link: '/guide/advanced/custom-renderer' },
+        // { text: 'Custom Renderers', link: '/guide/extras/custom-renderer' },
         // {
         //   text: 'Vue for React Devs',
-        //   link: '/guide/advanced/vue-for-react-devs'
+        //   link: '/guide/extras/vue-for-react-devs'
         // }
       ]
     }

src/about/faq.md

@@ -28,7 +28,7 @@ In stress-testing scenarios, Vue out-performs React and Angular by a decent marg
 
 Do note that synthetic benchmarks like the above focus on raw rendering performance with dedicated optimizations and may not be fully representative of real-world performance results. If you care more about page load performance, here is the [Lighthouse audit](https://www.webpagetest.org/result/210818_BiDcYB_4a83d7a1f2a7f6fdc76db16a00b4882d/) generated via [WebPageTest](https://www.webpagetest.org/lighthouse) for a real-world, Vue-powered site with SSG pre-rendering, full page hydration and SPA client-side navigations. It scores 98 in performance on an emulated Moto G4 with 4x CPU throttling over 3G networks.
 
-You can learn more about how Vue automatically optimizes runtime performance in the [Rendering Mechanism](/guide/advanced/rendering-mechanism.html) section, and how to optimize a Vue app in particularly demanding cases in the [Performance Optimization Guide](/guide/best-practices/performance.html).
+You can learn more about how Vue automatically optimizes runtime performance in the [Rendering Mechanism](/guide/extras/rendering-mechanism.html) section, and how to optimize a Vue app in particularly demanding cases in the [Performance Optimization Guide](/guide/best-practices/performance.html).
 
 ## Is Vue lightweight?
 
@@ -64,7 +64,7 @@ Please refer to the [dedicated Vue 2 vs. Vue 3 FAQ](./v2-faq).
 
 If you are new to Vue, we provide a high-level comparison between the two styles [here](/guide/introduction.html#which-to-choose).
 
-If you have previously used Options API and are currently evaluating Composition API, check out [this FAQ](/guide/advanced/composition-api-faq).
+If you have previously used Options API and are currently evaluating Composition API, check out [this FAQ](/guide/extras/composition-api-faq).
 
 ## Should I use JavaScript or TypeScript with Vue?
 
@@ -80,7 +80,7 @@ Vue was created before Web Components were natively available, and some aspects
 
 The Web Components specs are relatively low-level, as they are centered around defining custom elements. As a framework, Vue addresses additional higher-level concerns such as efficient DOM rendering, reactive state management, tooling, client-side routing, and server-side rendering.
 
-Vue also fully supports consuming or exporting to native custom elements - check out the [Vue and Web Components Guide](/guide/advanced/web-components) for more details.
+Vue also fully supports consuming or exporting to native custom elements - check out the [Vue and Web Components Guide](/guide/extras/web-components) for more details.
 
 <!-- ## TODO How does Vue compare to React? -->
 

src/api/built-in-directives.md

@@ -301,7 +301,7 @@
   <svg><a :xlink:special="foo"></a></svg>
   ```
 
-  When setting a binding on an element, Vue by default checks whether the element has the key defined as a property using an `in` operator check. If the property is defined, Vue will set the value as a DOM property instead of an attribute. This should work in most cases, but you can override this behavior by explicitly using `.prop` or `.attr` modifiers. This is sometimes necessary, especially when [working with custom elements](/guide/advanced/web-components.html#passing-dom-properties).
+  When setting a binding on an element, Vue by default checks whether the element has the key defined as a property using an `in` operator check. If the property is defined, Vue will set the value as a DOM property instead of an attribute. This should work in most cases, but you can override this behavior by explicitly using `.prop` or `.attr` modifiers. This is sometimes necessary, especially when [working with custom elements](/guide/extras/web-components.html#passing-dom-properties).
 
   The `.prop` modifier also has a dedicated shorthand, `.`:
 

src/api/component-instance.md

@@ -81,7 +81,7 @@
 
   Used to programmatically access content [distributed by slots](/guide/essentials/component-basics.html#content-distribution-with-slots). Each [named slot](/guide/components/slots.html#named-slots) has its own corresponding property (e.g. the contents of `v-slot:foo` will be found at `this.$slots.foo()`). The `default` property contains either nodes not included in a named slot or contents of `v-slot:default`.
 
-  Accessing `this.$slots` is most useful when writing a component with a [render function](/guide/advanced/render-function.html).
+  Accessing `this.$slots` is most useful when writing a component with a [render function](/guide/extras/render-function.html).
 
 - **Example:**
 
@@ -121,7 +121,7 @@
 - **See also:**
   - [`<slot>` Component](built-in-components.html#slot)
   - [Content Distribution with Slots](/guide/essentials/component-basics.html#content-distribution-with-slots)
-  - [Render Functions - Slots](/guide/advanced/render-function.html#slots)
+  - [Render Functions - Slots](/guide/extras/render-function.html#slots)
 
 ## $refs
 

src/api/options-rendering.md

@@ -63,4 +63,4 @@
   The `render` function has priority over the render function compiled from `template` option or in-DOM HTML template of the mounting element
   :::
 
-- **See also:** [Render Functions](/guide/advanced/render-function.html)
+- **See also:** [Render Functions](/guide/extras/render-function.html)

src/api/options-state.md

@@ -36,7 +36,7 @@
   data: vm => ({ a: vm.myProp })
   ```
 
-- **See also:** [Reactivity in Depth](/guide/advanced/reactivity-in-depth.html)
+- **See also:** [Reactivity in Depth](/guide/extras/reactivity-in-depth.html)
 
 ## props
 

src/guide/best-practices/security.md

@@ -184,4 +184,4 @@ HTTP security vulnerabilities, such as cross-site request forgery (CSRF/XSRF) an
 
 ## Server-Side Rendering (SSR)
 
-There are some additional security concerns when using SSR, so make sure to follow the best practices outlined throughout [our SSR documentation](/guide/advanced/server-side-rendering.html) to avoid vulnerabilities.
+There are some additional security concerns when using SSR, so make sure to follow the best practices outlined throughout [our SSR documentation](/guide/extras/server-side-rendering.html) to avoid vulnerabilities.