Client-only Routes & User Authentication
Often you want to create a site with client-only portions that are gated by authentication.
A classic example would be a site that has a landing page, various marketing pages, a login page, and then an app section for logged-in users. The logged-in section doesn’t need to be server rendered as all data will be loaded live from your API after the user logs in. So it makes sense to make this portion of your site client-only.
Gatsby uses @reach/router under the hood. You should use @reach/router to create client-only routes.
These routes will exist on the client only and will not correspond to index.html files in an app’s built assets. If you’d like site users to be able to visit client routes directly, you’ll need to set up your server to handle those routes appropriately.
To create client-only routes, add the following code to your site’s
💡 Note: There’s also a plugin to simplify the creation of client-only routes in your site: gatsby-plugin-create-client-paths.
Tip: For applications with complex routing, you may want to override Gatsby’s default scroll behavior with the shouldUpdateScroll Browser API.
Check out the “simple auth” example site for a demo implementing user authentication and restricted client-only routes.
Edit this page on GitHub