Professional catalog / “dex” demo: search, category filter, and detail pages over static JSON fixtures — no external data APIs. Intended for Vercel deploys with per-environment branding via NEXT_PUBLIC_* variables.
cd devdex
cp .env.example .env.local
npm install
npm run devOpen http://localhost:3000.
Set NEXT_PUBLIC_VERTICAL to one of:
| Value | Content |
|---|---|
devtools |
Libraries & tooling (default) |
retail |
Sample retail SKUs |
healthcare |
Fictional healthcare training stubs — not medical advice |
Data lives under src/data/verticals/<vertical>/.
See .env.example. Colors map to CSS variables on <html> (--color-bg, --color-accent, etc.). Optional NEXT_PUBLIC_LOGO_URL renders in the header.
| Command | Action |
|---|---|
npm run dev |
Dev server |
npm run build |
Production build |
npm run start |
Run production server locally |
npm run lint |
ESLint |
- Push this repo to GitHub (or GitLab / Bitbucket).
- New Project in Vercel → import the repo; framework Next.js is auto-detected.
- Set Environment Variables from
.env.example(at leastNEXT_PUBLIC_VERTICALif not using the default). - Deploy. Use Preview builds to validate alternate env sets.