package structure

Add a concise value statement that captures reader interest and previews content value. Focus on benefits while keeping it under two lines. Align with your blog categories.

## Apps Directory

**apps/web** - The main Next.js application. Contains all Payload CMS configuration, page routes, and app-specific code.

## Packages Directory

**packages/blocks** - Reusable content blocks (Hero, Feature, Pricing, etc.) used across pages.

**packages/primitives** - Base UI primitives (Link, Button, RichText) that blocks are built from.

**packages/shadcn** - Shadcn UI components with Radix primitives.

**packages/types** - Shared TypeScript types, primarily auto-generated from Payload CMS schema.

## Dependency Flow

web → blocks → primitives → shadcn

web → types

Each package can only depend on packages to its right, preventing circular dependencies.

Enterprise-Grade Monorepo Architecture

Core Contributors

Architectural Advantages

Incremental Builds

Shared Code

Atomic Deployments

Performance Metrics

10x

90%

<30s

package structure