Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Describe solution to centralized routing #2844

Merged
merged 4 commits into from
Aug 28, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -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/)
Expand Down Expand Up @@ -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>

Expand Down