Handling navigations in Remix
So far, we have used anchor tags to navigate between pages. You might have noticed that every navigation – using an anchor tag – triggers a full-page reload. This is the browser’s default behavior when navigating between pages. However, Remix also offers primitives for client-side navigations.
In this section, we will introduce you to Remix’s link components and Remix’s global navigation object. We will practice utilizing the navigation object to indicate page loads and learn more about server-side redirects with Remix.
Navigating with Remix’s link components
By default, a page navigation triggers a document request to the web server of the resource. The web server forwards the request to Remix (our HTTP request handler). Remix then renders a new document on the server to fulfill the request and responds with the rendered HTML document (or any other HTTP response).
