Layered domains
Repository → service → action → UI. Zod at the boundary.
Next.js 16 starter
Ship a bilingual staff back office without starting from zero.
App Router, Prisma RBAC, layered features, and a refined admin UI — ready to fork for your next product.
What you get
A production-oriented template
Public pages stay marketing-simple. Staff work lives in /admin with cookie sessions, permission gates, and URL-backed list screens.
en / id i18n
Cookie locale, prefixed routes, dictionaries as the source of copy.
Prisma staff RBAC
Roles, permissions, activity logs, and Super Admin bypass.
Built for forks
Conventions that scale
The same patterns Lencir uses in production — adapted so every new product starts with a calm, consistent back office.
Architecture
Clear layers so agents and humans know where new code belongs.
Bilingual by default
Every UI string lives in en and id dictionaries — no hardcoded copy.
Staff RBAC
Dashboard, users, roles, and audit logs gated by permission keys.
FAQ
Questions
Run the database seed, then open /admin/login with the SEED_SUPER_ADMIN_* credentials from .env.example.
Public URLs are /en and /id. A locale cookie plus proxy.ts remember the preference. Admin uses the same cookie without a URL prefix.
Create features/{name}/ with schemas, repositories, services, actions, and components. Wire a thin route in app/.
VPS via Docker + GHCR, or Vercel + Supabase Postgres. See docs/engineering/branching-and-deployment.md.