docs(parallel): clarify why separate slots cannot be static and dynam…

…ic at the same route segment level (#70386) ## Why? Currently, we do not explain why you cannot have a separate static and dynamic slot at the same route segment level. - Fixes #70366 --------- Co-authored-by: Zack Tanner <1939140+ztanner@users.noreply.github.com>
vercel · Sep 24, 2024 · 908b419 · 908b419
1 parent b3b7709
commit 908b419
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/02-app/01-building-your-application/01-routing/11-parallel-routes.mdx b/docs/02-app/01-building-your-application/01-routing/11-parallel-routes.mdx
@@ -64,7 +64,7 @@ export default function Layout({ children, team, analytics }) {
 }
 ```
 
-However, slots are **not** [route segments](/docs/app/building-your-application/routing#route-segments) and do not affect the URL structure. For example, for `/@analytics/views`, the URL will be `/views` since `@analytics` is a slot.
+However, slots are **not** [route segments](/docs/app/building-your-application/routing#route-segments) and do not affect the URL structure. For example, for `/@analytics/views`, the URL will be `/views` since `@analytics` is a slot. Slots are combined with the regular [Page](/docs/app/api-reference/file-conventions/page) component to form the final page associated with the route segment. Because of this, you cannot have separate [static](/docs/app/building-your-application/rendering/server-components#static-rendering-default) and [dynamic](docs/app/building-your-application/rendering/server-components#dynamic-rendering) slots at the same route segment level. If one slot is dynamic, all slots at that level must be dynamic.
 
 > **Good to know**:
 >