terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity

Describe solution to centralized routing (#2844)

Browse source 
* Add section for Centralized Routing

* Update title of section

* Update formatting

* Remove solution from README and link to it from FAQ
This commit is contained in:
Leon Daniel Thorne 2017-08-28 02:51:08 -04:00 committed by Arunoda Susiripala
parent eba9ebef5f
commit d2276179be
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
readme.md
View file

@ -1016,7 +1016,6 @@ So, you could only use `pathname`, `query` and `asPath` fields of the `context`
> Basically, you won't be able to render HTML content dynamically as we pre-build HTML files. If you need that, you need run your app with `next start`.
## Recipes
- [Setting up 301 redirects](https://www.raygesualdo.com/posts/301-redirects-with-nextjs/)
@ -1130,6 +1129,12 @@ Yes! Here's an example with [Apollo](./examples/with-apollo).
Yes! Here's an [example](./examples/with-redux)
</details>
<details>
<summary>Why aren't routes I have for my static export accessible in the development server?</summary>
This is a known issue with the architecture of Next.js. Until a solution is built into the framework, take a look at [this example solution](https://github.com/zeit/next.js/wiki/Centralizing-Routing) to centralize your routing.
</details>
<details>
<summary>Can I use Next with my favorite Javascript library or toolkit?</summary>