How we build
The stack behind every LuminaForge site.
Service business owners hire LuminaForge partly because the foundation is modern, fast, and auditable. This is the exact production stack on luminaforge.ai — and what we ship for client builds.
Production stack
What LuminaForge uses — and where to verify it.
No WordPress. No page builders. No jQuery. Every site is custom-engineered and you own the code from day one.
| Technology | Role | Detail | Live proof |
|---|---|---|---|
Next.js 16 | Application framework | App Router, React Server Components by default, Partial Prerendering, Turbopack in dev. No legacy pages/ directory. | View source on GitHub |
React 19 | UI runtime | Server Components for static shells; client leaves only where interactivity is required — Lumina chat, forms, motion. | This site |
Tailwind CSS v4 | Design system | CSS-first tokens in globals.css — no tailwind.config.ts. Semantic utilities (bg-background, text-primary) only. | Standards manifest |
Vercel Edge | Hosting + CDN | Global edge network, automatic HTTPS, preview deployments per PR, Speed Insights on production. | Live Core Web Vitals |
Velite MDX | Content pipeline | Typed MDX collections for work case studies and resources — builds to .velite/ at compile time, zero runtime MDX parser. | Case studies |
JSON-LD structured data | Search + AI entity clarity | Organization, WebSite, Service, FAQPage, Article, and BreadcrumbList on every route — computed from lib/seo helpers. | Schema coverage audit |
llms.txt + robots.txt | AI crawler policy | Compact and full company briefs for LLM crawlers; explicit allow rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and 8+ others. | robots.txt |
PageSpeed Insights | Performance verification | Weekly PSI refresh on marketing routes — LCP, INP, CLS, and Lighthouse scores published on the transparency dashboard. | Performance dashboard |
- Core Web Vitals in the green
- 12+ AI crawlers allowed
- FAQPage on every route
- Weekly PSI refresh
Same stack on every client build.
LuminaForge does not maintain WordPress or Wix installs. When a client migrates, they get the same architecture as this site: Next.js on Vercel, typed structured data, llms.txt, AI crawler permissions, and performance targets enforced in CI.
Your domain, your GitHub repo, your Vercel project — LuminaForge commits to your infrastructure from day one. If we ever part ways, you keep everything.
Ready to forge?
Let's build the site that becomes the answer.
Tell us about your project. We respond within one business day and book the first call inside a week.
FAQ
Questions about the LuminaForge stack.
6 answer-ready questions — semantic markup and FAQPage schema for search and AI assistants.
6 Q&As · FAQPage schema
Why does LuminaForge use Next.js instead of WordPress or Wix?
Page builders cap Core Web Vitals, custom schema, llms.txt, and AI crawler policy — the infrastructure AI assistants prefer before recommending a business. Next.js 16 with React Server Components ships phone-fast pages, typed structured data, and edge caching that WordPress plugins cannot match. LuminaForge documents the tradeoffs at /resources/wordpress-wix-vs-next-js-for-ai-search.
What is Partial Prerendering and why does it matter?
Partial Prerendering (PPR) is the default in Next.js 16 — static HTML shells prerender at build time while dynamic segments stream in. LuminaForge marketing routes stay fast on first paint without sacrificing live data where needed (transparency snapshots, gated content). Client sites get the same architecture.
How does LuminaForge prove performance claims?
LuminaForge publishes Core Web Vitals and Lighthouse scores weekly on /transparency, sourced from Google PageSpeed Insights. Case studies like We&Co include same-network before/after audits with real millisecond timings — not pitch-deck rounding.
What structured data does LuminaForge ship on client sites?
Organization or LocalBusiness, WebSite, Service, FAQPage, Article (for case studies and resources), and BreadcrumbList at minimum. Schema types are computed from the live route map — coverage is auditable on the transparency dashboard.
Does LuminaForge allow AI crawlers on client sites?
Yes — by default. LuminaForge explicitly allows GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and other major LLM crawlers in robots.txt. Blocking AI crawlers is a common reason businesses stay invisible in ChatGPT and Perplexity answers.
Can my IT team audit the stack before we commit?
Yes. LuminaForge commits to your GitHub, deploys on your Vercel project, and documents the stack on this page. Request a free AI Visibility Snapshot at /contact?offer=ai-visibility-snapshot for a plain-English read on your current platform vs what a Next.js build would change.