Route modules

Every built-in page is an object with a loader that fetches its data, a head that sets its tags, and a Component that draws it.

Take over one built-in page: point its path at your own route file, reuse the module's loader and head, and swap or wrap its Component.

The store's home page: loads the blocks the merchant arranged and draws each one with the component registered for its path.

The home block registry, re-exported beside the Home module: register which component draws each kind of block before any page renders.

The product page: loads one product by id with its breadcrumbs, and gives it full search-engine tags, including schema.org Product data.

One module behind every product grid: categories, search, tags, brand pages, and the latest, best-selling and offers lists.

The cart page, whose loader returns only a title because the visitor's cart id exists in the browser, not on the server.

A merchant's content page, such as About us or Terms: loads it by id and shows its HTML and comments.

The blog home page with featured slides, categories and latest articles, rendering empty lists rather than an error when the blog fails to load.

One blog article with its related articles, likes and comments, using the article's own SEO title, description and image when set.

Blog article lists filtered by one author, one category or one tag, each with the category sidebar and more articles as the reader scrolls.

The A to Z brands directory: every brand logo, grouped by first letter, each linking to that brand's product list.

The store reviews page, whose loader only sets a title while Salla's comments web component loads and sorts the reviews in the browser.

The loyalty program page, listing ways to earn points and prizes to redeem, or a 404 page when the store runs no program.

The order confirmation page Salla sends shoppers to after paying, which renders even when the order details cannot be loaded.

The signed-in customer's profile and account settings pages, built from Salla's ready-made web components and refused to guests.

The signed-in customer's order history, optionally filtered by status, as a table that loads more orders on request.

One order's details for its customer: items, amounts, shipping and status, with reorder, cancel, receipt and rating actions.

The signed-in customer's saved products, starting from the ?page= in the address and loading further pages as they scroll.

The signed-in customer's wallet balance and transaction history, starting from the ?page= in the address and loading more as they scroll.

The signed-in customer's notifications, such as order status changes, as one list with read and unread styling.

Loaders that render nothing and redirect: old /<slug>/brand-<id> links to the brand's product list, and /pending-orders to the orders list.

ProductListing's head function on its own: title, canonical and share tags for any product list, from its category or tag when there is one.

The pieces of ProductListLoaderData: page metadata, the source and its entity, the sort query and the tag shape, plus an unused category props type.

The shapes of blog articles, authors, categories and tags that the blog loaders return, for typing your own blog components.

The order shapes the account and thank-you pages use: a full order, one line of it, and the lighter row the orders list returns.

A lightweight index of shared route types, locale helpers and one redirect loader; route modules themselves live only on the granular subpaths.