Repository: vercel/next.js
Pull request: Next IA 2.0: Create Route Groups API reference, simplifying wording

Closes: https://linear.app/vercel/issue/DOC-4676/dynamic-route-segments-api-reference
Redirects: https://github.com/vercel/front/pull/46032

Changed files:
filename: docs/01-app/01-getting-started/02-project-structure.mdx
patch: @@ -81,10 +81,10 @@ Top-level files are used to configure your application, manage dependencies, run
 
 ### Route Groups and private folders
 
-|                                                                                   |                                                  |
-| --------------------------------------------------------------------------------- | ------------------------------------------------ |
-| [`(folder)`](/docs/app/building-your-application/routing/route-groups#convention) | Group routes without affecting routing           |
-| [`_folder`](#private-folders)                                                     | Opt folder and all child segments out of routing |
+|                                                                                |                                                  |
+| ------------------------------------------------------------------------------ | ------------------------------------------------ |
+| [`(folder)`](/docs/app/api-reference/file-conventions/route-groups#convention) | Group routes without affecting routing           |
+| [`_folder`](#private-folders)                                                  | Opt folder and all child segments out of routing |
 
 ### Parallel and Intercepted Routes
 

filename: docs/01-app/03-building-your-application/01-routing/08-route-groups.mdx
patch: @@ -1,27 +0,0 @@
----
-title: Route Groups
-description: Route Groups can be used to partition your Next.js application into different sections.
----
-
-In the `app` directory, nested folders are normally mapped to URL paths. However, you can mark a folder as a **Route Group** to prevent the folder from being included in the route's URL path.
-
-This allows you to organize your route segments and project files into logical groups without affecting the URL path structure.
-
-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:
-  - Creating multiple nested layouts in the same segment, including multiple root layouts
-  - Opting specific segments into a layout
-- Opting for loading skeletons on a specific route
-
-## Convention
-
-A route group can be created by wrapping a folder's name in parenthesis: `(folderName)`
-
-> **Good to know**:
->
-> - 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/page.js` and `(shop)/about/page.js` would both resolve to `/about` and cause an error.
-> - If you use multiple root layouts without a top-level `layout.js` file, your home `page.js` file should be defined in one of the route groups, For example: `app/(marketing)/page.js`.
-> - Navigating **across multiple root layouts** will cause a **full page load** (as opposed to a client-side navigation). For example, navigating from `/cart` that uses `app/(shop)/layout.js` to `/blog` that uses `app/(marketing)/layout.js` will cause a full page load. This **only** applies to multiple root layouts.

filename: docs/01-app/05-api-reference/03-file-conventions/layout.mdx
patch: @@ -114,7 +114,7 @@ export default function RootLayout({ children }) {
 
 - The root layout **must** define `<html>` and `<body>` tags.
   - You should **not** manually add `<head>` tags such as `<title>` and `<meta>` to root layouts. Instead, you should use the [Metadata API](/docs/app/getting-started/metadata-and-og-images) which automatically handles advanced requirements such as streaming and de-duplicating `<head>` elements.
-- You can use [route groups](/docs/app/building-your-application/routing/route-groups) to create multiple root layouts.
+- You can use [route groups](/docs/app/api-reference/file-conventions/route-groups) to create multiple root layouts.
   - Navigating **across multiple root layouts** will cause a **full page load** (as opposed to a client-side navigation). For example, navigating from `/cart` that uses `app/(shop)/layout.js` to `/blog` that uses `app/(marketing)/layout.js` will cause a full page load. This **only** applies to multiple root layouts.
 
 ## Caveats

filename: docs/01-app/05-api-reference/04-functions/use-selected-layout-segments.mdx
patch: @@ -46,7 +46,7 @@ export default function ExampleClientComponent() {
 > **Good to know**:
 >
 > - Since `useSelectedLayoutSegments` is a [Client Component](/docs/app/getting-started/server-and-client-components) hook, and Layouts are [Server Components](/docs/app/getting-started/server-and-client-components) by default, `useSelectedLayoutSegments` is usually called via a Client Component that is imported into a Layout.
-> - The returned segments include [Route Groups](/docs/app/building-your-application/routing/route-groups), which you might not want to be included in your UI. You can use the `filter()` array method to remove items that start with a bracket.
+> - The returned segments include [Route Groups](/docs/app/api-reference/file-conventions/route-groups), which you might not want to be included in your UI. You can use the [`filter`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/filter) array method to remove items that start with a bracket.
 
 ## Parameters