remove unnecessary deep page outlines

Author: yyx990803

src/guide/built-ins/transition.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 <script setup>
 import Basic from './transition-demos/Basic.vue'
 import SlideFade from './transition-demos/SlideFade.vue'

src/guide/components/events.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Component Events
 
 > This page assumes you've already read the [Components Basics](/guide/essentials/component-basics). Read that first if you are new to components.

src/guide/components/props.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Props
 
 > This page assumes you've already read the [Components Basics](/guide/essentials/component-basics). Read that first if you are new to components.

src/guide/components/provide-inject.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Provide / Inject
 
 > This page assumes you've already read the [Components Basics](/guide/essentials/component-basics). Read that first if you are new to components.
@@ -99,7 +95,7 @@ However, do note this does **not** make the injection reactive. We will discuss
 
 </div>
 
-### App-level Provide
+## App-level Provide
 
 In addition to providing data in a component, we can also provide at the app level:
 

src/guide/components/slots.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Slots
 
 > This page assumes you've already read the [Components Basics](/guide/essentials/component-basics). Read that first if you are new to components.

src/guide/essentials/class-and-style.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Class and Style Bindings
 
 A common need for data binding is manipulating an element's class list and its inline styles. Since they are both attributes, we can use `v-bind` to handle them: we only need to calculate a final string with our expressions. However, meddling with string concatenation is annoying and error-prone. For this reason, Vue provides special enhancements when `v-bind` is used with `class` and `style`. In addition to strings, the expressions can also evaluate to objects or arrays.

src/guide/essentials/event-handling.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Event Handling
 
 ## Listening to Events

src/guide/reusability/composables.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Composables
 
 <script setup>

src/guide/scaling-up/ssr.md

@@ -265,14 +265,24 @@ However, in an SSR context, the application modules are typically initialized on
 
 We can technically re-initialize all the JavaScript modules on each request, just like we do in browsers. However, initializing JavaScript modules can be costly, so this would significantly affect server performance.
 
-The recommended solution is to create a new instance of the entire application - including the router and global stores - on each request:
+The recommended solution is to create a new instance of the entire application - including the router and global stores - on each request. The, instead of directly importing it in our components, we provide the shared state using [app-level provide](/guide/components/provide-inject.html#app-level-provide) and inject it in components that need it:
 
 ```js
+// app.js (shared between server and client)
+import { createSSRApp } from 'vue'
+import { createStore } from './store.js'
 
+export function createApp() {
+  const app = createSSRApp(/* ... */)
+  // create new instance of store per request
+  const store = createStore(/* ... */)
+  // provide store at the app level
+  app.provide('store', store)
+  // also expose store for hydration purposes
+  return { app, store }
+}
 ```
 
-create a fresh instance of the application and the shared object on each request. Then, instead of directly importing it in our components, we provide the shared state using [app-level provide](/guide/components/provide-inject.html#app-level-provide) and inject it in components that need it.
-
 State Management libraries like Pinia are designed with this in mind. Consult [Pinia's SSR guide](https://pinia.vuejs.org/ssr/) for more details.
 
 ### Hydration Mismatch

src/guide/scaling-up/testing.md

@@ -1,7 +1,3 @@
----
-aside: deep
----
-
 # Testing
 
 ## Overview