Skip to content

Commit

Permalink
docs(v2): fix pages routing inaccurate info (#2110)
Browse files Browse the repository at this point in the history
* docs(v2): fix pages routing inaccurate info

* fix CI
  • Loading branch information
endiliey authored and yangshun committed Dec 10, 2019
1 parent bbc1d2c commit 9b5266a
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 4 deletions.
3 changes: 2 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,8 @@
"git add"
],
"*.md": [
"yarn prettier-docs"
"yarn prettier-docs",
"git add"
]
},
"husky": {
Expand Down
6 changes: 3 additions & 3 deletions website/docs/creating-pages.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,10 +45,10 @@ Each page doesn't come with any styling. You will need to import the `Layout` co

If you are familiar with other static site generators like Jekyll and Next, this routing approach will feel familiar to you. Any JavaScript file you create under `/src/pages/` directory will be automatically converted to a website page, following the `/src/pages/` directory hierarchy. For example:

- `/src/pages/index.js``<baseUrl>/`
- `/src/pages/test.js``<baseUrl>/test`
- `/src/pages/index.js``<baseUrl>`
- `/src/pages/foo.js``<baseUrl>/foo`
- `/src/pages/foo/test.js``<baseUrl>/foo/test`
- `/src/pages/foo/index.js``<baseUrl>/foo`
- `/src/pages/foo/index.js``<baseUrl>/foo/`

In this component-based development era, it is encouraged to co-locate your styling, markup and behavior together into components. Each page is a component, and if you need to customize your page design with your own styles, we recommend co-locating your styles with the page component in its own directory. For example, to create a "Support" page, you could do one of the following:

Expand Down

0 comments on commit 9b5266a

Please sign in to comment.