Skip to main content
Skip to content
Template Empire
Admin Dashboardv1.25.31
Live DemoView template

Last updated on 4 June 2026

Frequently Asked Questions

What stack does this template use?

The full-stack templates use Next.js App Router, React, TypeScript, Tailwind CSS v4, PostgreSQL, Drizzle ORM, Zod validation, and pnpm. Individual template editions may add domain-specific dependencies such as Stripe, charts, uploads, or scheduling primitives.

Check package.json for the exact versions included in your ZIP.

Is this a static template or a real full-stack app?

It is a real full-stack app. It includes server-rendered pages, API routes, PostgreSQL schema/migrations, authentication, account settings, compliance routes, email flows, and operational scripts.

Some live-demo deployments use mock data so public previews can run without a production database. Buyer ZIPs are intended to run against PostgreSQL.

Which database should I use?

Use PostgreSQL. The local demo setup can run PostgreSQL with Docker Compose. For production you can use providers such as Supabase, Neon, Railway, Render, Fly, or another PostgreSQL host.

How do I change the product name?

Edit src/lib/site-config.ts. Start with:

  • SITE_CONFIG.productName
  • SITE_CONFIG.brandName
  • SITE_CONFIG.companyName
  • SITE_CONFIG.legalEntity
  • SITE_CONFIG.contact
  • SITE_CONFIG.urls

Then search the codebase for any remaining product copy you want to replace.

How do I change colours and fonts?

Use src/app/globals.css for semantic colour tokens and font-role mappings. If your template uses next/font, font loading will usually be in src/app/layout.tsx. If your template ships files under src/themes/, those files may contain edition-level overrides.

Keep colours semantic so dark mode, focus rings, badges, charts, and forms inherit the brand system consistently.

See DESIGN_TOKENS.md for the full token workflow.

Can I use this for client projects?

See LICENCE.md for the exact commercial terms. In general, buyer-facing apps should be rebranded before public launch so users see your product and legal entity, not template placeholder content.

Do I need OAuth or email providers to test locally?

No. Email/password auth and seeded demo users work locally without OAuth. For full buyer testing, add your OAuth and email provider keys to .env or .env.local using the variable names documented in .env.example.

Why do some docs mention demo mode?

There are two separate demo concepts:

  • DEMO_MODE is a server-side flag for in-dashboard demo/mock behaviour.
  • NEXT_PUBLIC_TE_DEMO is only for marketplace live previews and displays a demo notice.

Do not set NEXT_PUBLIC_TE_DEMO on a buyer production deployment.

How do I run the template locally?

Follow INSTALLATION.md. The usual flow is:

bash
cp .env.example .env
docker compose -f docker-compose.demo.yml up -d
pnpm install
pnpm db:migrate
pnpm db:seed
pnpm dev

Some template editions use a more specific seed command. If so, the edition's INSTALLATION.md will list it.

Where should I report issues?

Use the issue tracker for the repository you received or the support channel listed with your purchase. Include your template version, Node/pnpm versions, the command you ran, and the relevant terminal output.