Next.js

What every page of your site is written in, including this one.

THE FOUNDATION

ON THIS BUILD: USED ON THIS BUILD
WHERE IT RUNS: Runtime · Vercel · App Router
OFFICIAL DOCS: Read the reference →

What it is

The framework every page of your site is written in. It renders real pages on a server, on the edge, before your customer ever asks for them — which is why a Nimos site loads like a local file and every section has a real address Google can index.

What it does for your business

For your business it means speed you keep: fast pages on a phone over hotel Wi-Fi, every service and location its own indexable address, and no blank-screen moments where a customer gives up and calls the next listing.

Why it earns its place

Every route is a real server-rendered page with its own address. The framework is the difference between a site Google can index and a canvas that renders after a blank screen.

This very site is built on it — you are reading one of its routes right now.

THE TOOL

Open Next.js Read the official docs →

This checkout, not a demo

USED ON THIS BUILD

Route manifests

Published components

116

Type check

0 errors

Production build

0 errors

Counts are derived from lib/build-story/summary.json; the build-story gate re-derives that file from the .tsx on disk.

How it runs here

The App Router renders server components first. Dynamic owner pages use `generateStaticParams` to publish every engine file at build time; shared chrome, metadata and security headers come from the layout and `next.config.ts`.

APP ROUTER / STATIC PARAMS

export function generateStaticParams() {  return ENGINES.map(({ slug }) => ({ engine: slug }));} export default async function EnginePage({ params }) {  const { engine } = await params;  const doc = engineBySlug(engine);  if (!doc) notFound();}

When it runs

Every page, every build. A new route is a folder with a page file, not a card in a builder.

Who owns it

Build owns the route tree. QA owns the gates: type check, production build, link crawl, then a real browser at 390 and 1440.

What it does not claim

The route count is this checkout's published build-story count, not a promise about a future page. Dynamic routes can add runtime pages the manifest does not list.

THE REFERENCE

The manual above is ours. The vendor's reference is the place to check an API, a version or a limit.

Open the official docs →

This is the tool. The process is what turns it into your business.

File the brief