FAQ
Frequently asked questions about licensing, scope, customization, and troubleshooting.
Table of Contents
- Frequently Asked Questions
- Common Support Issues
- Build Failures
- Deployment Failures
- Theme Customization Questions
- Browser Support
- Updating Dependencies
Frequently Asked Questions
Can I use this for client projects?
Yes. A Regular License covers one end product used by you or a single client; you may not resell or redistribute the template's source files themselves. If you're building for multiple clients or reselling products built with this template, you need the Extended License. See Getting Started and the licensing terms on the marketplace listing.
Does it include a backend or database?
No. This is a frontend-only template. There is no backend, database, or authentication system anywhere in the project. The login, register, and forgot-password pages are UI forms only — submitting them does nothing. See the Authentication section on Launchpad and Lumina — the same UI-only pages are included in Forge as well.
Can I change the colors and fonts?
Yes. Full walkthrough: Customization.
How do I deploy to Vercel?
Each of the three variants deploys as its own Vercel project. Full walkthrough: Deployment.
Is dark mode included?
Yes, on all three variants. Lumina defaults to dark; Launchpad and Forge default to the visitor's system preference. See Customization.
What is included in the Figma file?
Design tokens (color/typography/radius), a shared components page, and all three variants at desktop and mobile frame sizes, with annotation notes on interactive/animated behavior. The Figma file is delivered separately from the code.
How do I add new blog posts?
Add a new Markdown file to the relevant variant's blog content folder with the required fields. No extra setup or registration needed. Full walkthrough: Customization.
Can I use this with a headless CMS?
Yes, but you'll need to connect it yourself. Blog and documentation content currently comes from local Markdown files. To source content from a headless CMS instead, you'll need to replace the content-loading logic with calls to your CMS, while keeping the same content structure the templates expect.
What support is included?
See the license-based support tiers and response targets in Getting Started.
Is there a search feature in the Forge documentation section?
No, the documentation section in the Forge variant doesn't currently include a search feature. See Forge.
Does the AI Demo in Lumina actually call an AI model?
No. It's a scripted animation over example prompts/responses — there is no live model connected. See Lumina.
Common Support Issues
The most common questions buyers raise, roughly in order of frequency:
- Confusion about the lack of a backend/authentication (see above — this is by design)
- "How do I change X color / logo / text" — almost always answered in Customization
- Installation failing to complete — almost always caused by using npm/yarn instead of pnpm, see Installation
- Vercel deployment showing a 404 or the wrong variant — almost always a Root Directory misconfiguration, see Deployment
Build Failures
| Symptom | Likely cause | Fix |
|---|---|---|
| "Cannot find module" errors | Installed with npm/yarn instead of pnpm, or ran the install command from inside a variant folder instead of the project root | Reinstall with pnpm install from the project root |
| Build fails after adding a package | Dependency changes weren't fully saved before building | Reinstall dependencies and try again |
More detail in Installation.
Deployment Failures
| Symptom | Likely cause | Fix |
|---|---|---|
| Vercel build fails immediately, can't find the project | Root Directory not set to a specific variant folder | Set Root Directory to the correct variant folder per project |
| Build succeeds locally, fails on Vercel | Dependency changes weren't fully committed before deploying | Reinstall and redeploy with all changes committed |
| Wrong variant appears at your custom domain | Domain attached to the wrong Vercel project | Re-check Project → Settings → Domains on each of the three projects |
More detail in Deployment.
Theme Customization Questions
"I changed my brand color but some elements are still the old color." Check whether the color you're seeing is one of the documented exceptions (Lumina's gradient orbs, Forge's method badges, code syntax highlighting, status colors) rather than the main brand color — these are intentionally kept separate. See Customization.
"I changed the shared color settings and it changed the colors in all three variants, not just one." That's expected — the color settings are shared by default. Override colors per-variant instead if you want variant-specific colors.
"My new font isn't showing up." Confirm you updated the font selection in every variant you want it to affect — each variant configures its own fonts independently.
Browser Support
Cross-browser behavior (layout, animations, dark mode, forms) was manually verified across current versions of Chrome, Firefox, Safari, and Edge, at common screen sizes from mobile through desktop.
This template targets evergreen, auto-updating browsers. It relies on modern web features and is not tested against, and is unlikely to work correctly in, legacy browsers such as Internet Explorer.
Updating Dependencies
If you'd like to update the packages this project depends on:
- Check what's outdated.
- Update the packages you want to upgrade.
- Reinstall and confirm the project still builds and runs correctly.
Warning
Pay particular attention when updating Next.js and React — major version bumps can require code changes. Re-run the full Production Checklist after any major upgrade.