Скачать или смотреть Gatsby Unified Routes, with Blaine Kasten

Blaine Kasten is a Staff Software Engineer on the Core team at Gatsby.

A crucial part of building any website is the routing structure: what pages exist and how they’re built. One way to manage routes is the file system: components inside `src/pages` directory are turned into pages at build time. However, a few common use cases, including client-side routing and generating pages for each element of a collection, are currently not possible using the file system. `createPages` is a low-level API that allows you to do anything related to page creation, but it’s meant to be an advanced feature. Website creators shouldn’t have to delve into Gatsby Node APIs to accomplish key goals. Blaine introduced Unified Routing, a suite of new APIs and conventions to make the file system the primary way of building pages.

Unified Routing is still in development and builds on the fundamental `createPages` API. Now, dynamic URL segments, i.e. client-side routing, can be indicated by creating a `/src/pages/order/[id].js` file, as opposed to using the `matchPath` property in the `createPage` API. The id is given to the component at runtime through a key called `params`. Collection Routing addresses the other use case. To generate pages for every collection item, we want to fetch data and generate pages at build time. The export statement will use `createPagesFromData`, a macro that will create the specified component for every entry in the data queried, e.g. `/product/Burger`, `/product/Chicken`. An additional benefit of Unified Routing is that you can see what routes your site has at a glance.

Ready to try it out? Try our canary release by running yarn install gatsby@unifiedroutes and please share your feedback on our RFC (https://gatsby.dev/unified-routes-rfc). Lastly, don't forget to connect with Blaine on Twitter @blainekasten!