GEM CYBER Enterprise Platform

Next.js 16 App Router experience with:

• One-page enterprise marketing surface (/) with anchored sections.
• Intelligence Command Center (/intelligence).
• Email Campaign Engine UI shell (/campaigns).
• Architecture/specification route (/specs).
• Architecture alias route (/architecture).
• Admin center with role-based auth (/admin/*).

Local development

1. Install dependencies:

npm install

2. Configure environment values:

cp .env.example .env.local

3. Start the dev server:

npm run dev

4. Open in browser:

• Public app: http://localhost:3000
• Intelligence module: http://localhost:3000/intelligence
• Campaign module: http://localhost:3000/campaigns
• Specs route: http://localhost:3000/specs
• Architecture alias: http://localhost:3000/architecture
• Admin login: http://localhost:3000/admin/login

Required environment variables

NEXT_PUBLIC_APP_NAME="GEM CYBER"
NEXT_PUBLIC_SUPPORT_EMAIL="admin@gemcybersecurityassist.com"
NEXT_PUBLIC_SUPPORT_PHONE="(xxx) xxx-xxxx"
DATA_PROVIDER_API_KEY=""
NEWS_INGESTION_WEBHOOK_SECRET=""
EMAIL_PROVIDER_API_KEY=""
EMAIL_SENDING_DOMAIN=""
DATABASE_URL=""
AUDIT_LOG_SINK=""

Admin and SMTP values are also defined in .env.example for local auth + email testing.

Quality checks

npm run lint
npm run build

Tailwind setup

Tailwind is configured through the Next.js build pipeline (no CDN dependency):

• src/app/globals.css imports tailwindcss.
• PostCSS plugin is configured in postcss.config.mjs.
• Production builds compile styles with npm run build.

Vercel deployment

1. Import repository in Vercel.
2. Set framework preset to Next.js.
3. Add environment variables from .env.example.
4. Configure:
   • Build command: npm run build
   • Output: .next (automatic)
5. Enable previews for branch pushes.
6. Keep production deployment mapped to main.

Suggested branch workflow

git checkout -b feat/master-onepage-rebrand
git push -u origin feat/master-onepage-rebrand

After preview validation in Vercel, open a PR into main.

Deployment smoke checks

After deployment, verify canonical routes and redirects:

curl -I https://<your-domain>/home
curl -I https://<your-domain>/contact
curl -s https://<your-domain>/api/health
curl -s https://<your-domain>/api/routes

Expected behavior:

• /home redirects to /
• /contact redirects to /contact-us
• /api/health returns { "ok": true, ... }
• /api/routes returns route + redirect registry JSON

Notes

• Campaign data model stubs live in src/lib/campaigns/models.ts and map to contacts, segments, campaigns, recipients, events, suppression_list, audit_logs, and notification_outbox.
• File-based inbox and admin data stores are suitable for development but should be moved to managed persistence for production.