Pages

2. Deploy via CLI

# First deployment creates the project
wrangler pages deploy ./dist --project-name my-site

# Subsequent deployments
wrangler pages deploy ./dist --project-name my-site

3. Or Connect Git (Dashboard)

1. Cloudflare Dashboard > Workers & Pages > Create
2. Connect GitHub or GitLab
3. Select repository
4. Configure build command and output directory
5. Deploy

4. Add Server-Side Functions

// functions/api/data.ts
export const onRequestGet: PagesFunction = async (context) => {
  return Response.json({ message: 'Hello from the edge!' });
};

5. Add Bindings

# wrangler.toml
[[d1_databases]]
binding = "DB"
database_name = "my-db"
database_id = "xxx"

Framework Presets

Functions Routing

functions/
├── api/
│   ├── hello.ts         → /api/hello
│   ├── users/
│   │   ├── index.ts     → /api/users
│   │   └── [id].ts      → /api/users/:id
│   └── [[path]].ts      → /api/* (catch-all)
└── _middleware.ts        → Runs before all routes

Limits

Edge Cases

• Preview URLs: <hash>.<project>.pages.dev and <branch>.<project>.pages.dev.
• _redirects and _headers files in output directory for custom rules.
• Pages Functions share the same runtime constraints as Workers.
• Next.js requires @cloudflare/next-on-pages adapter for full compatibility.
• Environment variables set via wrangler pages secret put or dashboard.