Route Groups
In the app directory, nested folders are typically mapped to URL paths. However, you can designate a folder as a Route Group to exclude it from the route's URL path. This is useful when you want to organize your routes into subdirectories without changing the URL structure.
This allows you to organize your route segments and project files into logical groups without affecting the URL path structure. It provides a convenient way to group related routes together and improve the overall organization of your application.
Route groups are useful for:
- Organizing routes into groups e.g. by site section, intent, or team.
- Enabling nested layouts in the same route segment level:
- For example, you can have a
layout.php
file in theapp/admin
directory that is used for all routes in theadmin
group.
- For example, you can have a
Convention
A route group can be created by wrapping a folder's name in parenthesis: (folderName)
Examples
Organize routes without affecting the URL path
To organize routes without affecting the URL, create a group to keep related routes together. The folders in parenthesis will be omitted from the URL (e.g. (marketing)
or (shop)
).
Even though routes inside (marketing)
and (shop)
share the same URL hierarchy, you can create a different layout for each group by adding a layout.php
file inside their folders.
Opting specific segments into a layout
To opt specific routes into a layout, create a new route group (e.g. (shop)
) and move the routes that share the same layout into the group (e.g. account
and cart
). The routes outside of the group will not share the layout (e.g. checkout
).
- The naming of route groups has no special significance other than for organization. They do not affect the URL path.
- Routes that include a route group should not resolve to the same URL path as other routes. For example, since route groups don't affect URL structure,
(marketing)/about/index.php
and(shop)/about/index.php
would both resolve to/about
and cause an error. - Navigating across multiple root layouts will cause a full page load (as opposed to a client-side navigation). For example, navigating from
/cart
that usesapp/(shop)/layout.php
to/blog
that usesapp/(marketing)/layout.php
will cause a full page load. This only applies to multiple root layouts.