Describe solution to centralized routing (#2844)

* Add section for Centralized Routing

* Update title of section

* Update formatting

* Remove solution from README and link to it from FAQ

readme.md

@@ -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>