@@ -184,13 +184,13 @@ When the `perPagePosts` is set to `2`, this plugin will help you generate the fo
184184| ` /2018/06/08/c/ ` | ` Post ` |
185185
186186::: tip
187- ` DirectoryPagination / Layout ` means that the layout component will Will be downgraded to ` Layout ` when ` DirectoryPagination ` layout doesn't exist.
187+ ` DirectoryPagination / Layout ` means that the layout component will be downgraded to ` Layout ` when ` DirectoryPagination ` layout doesn't exist.
188188:::
189189
190190So how to get the matched pages in the layout component? In fact, it will be much simpler than you think.
191191
192- If you visit ` / ` , current page leverages layout ` IndexPost ` , in this layout component, you just need to use `this
193- .$pagination.pages` to get the matched pages, in the above example, the actual value of ` this.$pagination.pages` will
192+ If you visit ` / ` , current page leverages layout ` IndexPost ` . In this layout component, you just need to use
193+ ` this .$pagination.pages` to get the matched pages. In the above example, the actual value of ` this.$pagination.pages ` will
194194 be:
195195
196196``` json
@@ -200,20 +200,20 @@ If you visit `/`, current page leverages layout `IndexPost`, in this layout comp
200200]
201201```
202202
203- If you visit ` / ` , current page leverages layout ` DirectoryPagination ` , you can also use `this
204- .$pagination.pages` to access it:
203+ If you visit ` / ` , current page leverages layout ` DirectoryPagination ` , you can also use
204+ ` this .$pagination.pages` to access it:
205205
206206``` json
207207[
208208 { "relativePath" : " _posts/2019-6-8-c.md" , "path" : " /2019/06/08/c/" ... },
209209]
210210```
211211
212- Isn't a very natural experiences ? You just need to care about the style of your layout component, not the complicated and boring logic behind it.
212+ Isn't this very natural experience ? You just need to care about the style of your layout component, not the complicated and boring logic behind it.
213213
214214
215215::: tip
216- To save the length of docs, we omitted the data structure of ` $page ` object. you can get more information about
216+ To save the length of docs, we omitted the data structure of the ` $page ` object. You can get more information about
217217the data structure of ` $page ` at the [ official documentation] ( https://v1.vuepress.vuejs.org/guide/global-computed.html#page ) .
218218:::
219219
@@ -265,22 +265,22 @@ module.exports = {
265265 // Layout of the `entry page`
266266 layout: ' Tag' ,
267267 },
268- ]
268+ ]
269269 }]
270270 ]
271271}
272272```
273273
274- Then the plugin will help you to generate following extra pages, and automatically leverage corresponding
275- layout:
274+ Then the plugin will help you to generate the following extra pages, and automatically leverage
275+ the corresponding layout:
276276
277277| url | layout |
278278| ---| ---|
279279| ` /tag/ ` | ` Tag ` |
280280| ` /tag/vue/ ` | ` FrontmatterPagination ` / ` Layout ` |
281281| ` /tag/js/ ` | ` FrontmatterPagination ` / ` Layout ` |
282282
283- In ` Tags ` component, you can use ` this.$tag.list ` to get the tag list. the value would be like:
283+ In the ` Tags ` component, you can use ` this.$tag.list ` to get the tag list. The value would be like:
284284
285285``` json
286286[
@@ -325,7 +325,7 @@ classification:
325325
326326## Examples
327327
328- Actually, there are only 2 necessary layouts components to create a blog theme:
328+ Actually, there are only 2 necessary layout components to create a blog theme:
329329
330330- Layout
331331- Post
0 commit comments