docs: api/router-view

Author: yyx990803

docs/en/api/options.md

@@ -0,0 +1 @@
+# Router Construction Options

docs/en/api/router-link.md

@@ -10,7 +10,7 @@
 
 - When you are using the `base` option in HTML5 history mode, you don't need to include it in `to` prop's URLs.
 
-#### Props
+### Props
 
 - **to**
 

docs/en/api/router-view.md

@@ -0,0 +1,27 @@
+# `<router-view>`
+
+The `<router-view>` component is a functional component that renders the matched component for the given path. Components rendered in `<router-view>` can also contain its own `<router-view>`, which will render components for nested paths.
+
+### Props
+
+- **name**
+
+  - type: `string`
+
+  - default: `"default"`
+
+  When a `<router-view>` has a name, it will render the component with the corresponding name in the matched route record's `components` option. See [Named Views](../essentials/named-views.md) for an example.
+
+### Behavior
+
+Any non-name props will be passed along to the rendered component, however most of the time the per-route data is contained in the route's params.
+
+Since it's just a component, it works with `<transition>` and `<keep-alive>`. When using the both together, make sure to use `<keep-alive>` inside:
+
+``` html
+<transition>
+  <keep-alive>
+    <router-view></router-view>
+  </keep-alive>
+</transition>
+```