AEAl-Andalus⺢Experience
Sign in · Join
AEAl-Andalus⺢Experience
ProjectsGalleryAboutArticlesDashboardAPI
© 2026 — Modular content systems☕buy me a coffee
Framework Study Guide
ChaptersCardsLegendRoadmapRoute Map
Cards
Card · LegendCard · Server PageCard · Client ComponentCard · Entity ActionsCard · Server ActionsCard · Context ProviderCard · API RouteCard · Types & PrismaCard · Entity-FirstCard · DeploymentCard · Next 16 + Prisma 7Card · CSS & TailwindCard · Libraries & AcceleratorsCard · Prisma 7 (Next App Router)Card · TypeORMCard · DrizzleCard · Special FilesCard · Client BoundariesCard · Next 16: cache, PPR, proxy, AI
→ chapters/02a-boundary-patterns

Card · Client Boundaries

Import contagion, islands of interactivity, and use() on the client.

Rules

  • "use client" propagates down the import tree — place it as deep as possible, never in layouts.
  • Client components are interactive islands in a sea of server content.
  • use(promise) (React 19) unwraps server-passed promises; replaces "fetch on mount" for initial data.
  • Entity truth stays on the server; client state is UI-only (filters, selection, layout).

Study Card · Chapter 02a-boundary-patterns