Applications in the Monorepo
The three Next.js apps — roles, ports, and links to full application guides.
Applications in the Monorepo
Three Next.js applications share @repo/* packages and (for web and admin) the same Appwrite project. This page summarizes how they differ and where the detailed guides live. It intentionally avoids duplicating the Applications section.
Summary
| App | Port (typical) | Audience | Canonical docs |
|---|---|---|---|
| web | 3000 | Public visitors | Web app |
| admin | 3001 | Editors and operators | Admin app |
| docs | 3002 | Developers (this site) | Content under apps/docs/content/docs/ |
Comparison
| Web | Admin | Docs | |
|---|---|---|---|
| Primary job | Serve public pages and flows | Create and manage content | Document the monorepo |
| Auth | User-facing (e.g. magic link) | Required for dashboard | None for static reading |
| Data | Reads (and writes where needed) | Read/write against Appwrite | Mostly static MDX |
| i18n | Yes (locales in routes) | Yes | English-first |
| Payments | Checkout and webhooks | Configuration, not checkout UI | N/A |
| Page builder | Renders published JSON | Edits with Puck | N/A |
Shared behavior
- Direct Appwrite access — Web and admin each use @repo/api (session or admin clients). There is no private app-to-app HTTP API for normal CRUD; both talk to the same backend. See Data flow.
- Shared UI — @repo/ui is used across web, admin, and docs.
- Independent deploys — Each app can be built and deployed on its own (separate domains or paths).
Local development
bun run dev --filter=web
bun run dev --filter=admin
bun run dev --filter=docsRepository layout for apps: see Project structure.
ℹ️
Go deeper
Use Applications overview for role-based entry points, then open the web or admin guides for routing, features, and implementation notes.