Next.js site
A short, non-technical overview of what powers these pages, how updates go live, and why that approach has real advantages.
This site is built with Next.js and hosted with Vercel.
The site isn't a WordPress-style website where someone logs in to a dashboard and types posts. It's built in Cursor — an AI-assisted editor where I work on the site's content and design directly, with the AI helping write the underlying code.
When I'm ready to publish, the changes push to Vercel, which rebuilds the site and puts the update live worldwide in seconds.
The result is a site that's faster, more secure, and more flexible than a traditional CMS, because there's no database or admin panel exposed to the internet — the live site is essentially a pre-built, high-performance version of the source files.
Every framework, UI library, and utility declared in code — auditable, version-controlled, and portable. No opaque plugin marketplace.
Read moreVS Code-compatible, AI-assisted code editor. The developer works on source files — not a browser dashboard. Nothing runs inside Cursor.
Read moreGit push triggers a worldwide production build. HTTPS automatic, atomic deploys, instant rollback — no server to SSH into.
Read moreFrom local editing to a global deploy — a straightforward pipeline without a traditional CMS in the middle.
Content and design live in the same workflow as the code. Cursor is an AI-assisted editor where I shape pages and features directly, with the model helping write and refine the underlying React and Next.js code.
Changes stay in the project until you are ready. You can preview the real site experience before anything is published, without logging into a separate “site admin” on the public internet.
When it is time to go live, updates are pushed to the host. Vercel runs a fresh production build and rolls out the new version worldwide in seconds across its global network.
Visitors get pre-rendered, optimized pages. There is no WordPress-style dashboard or database serving every page request in the same way a traditional CMS might.
How a business request becomes a live update without a WordPress admin in the middle. The client approves on real URLs; the developer keeps the source of truth in Git and the host in part 3 above.
Client approves?
WordPress is a fine product for many use cases, but a Next.js site is a different class of system. The labels are not interchangeable: one is a PHP and database application with a web admin, the other is a modern web application you ship as a build from source.
A CMS in the original sense
A compiled web app, not a browser-based CMS for day-to-day editing
Why a Next.js site on Vercel, maintained from Cursor, compares favorably to a classic CMS for this kind of build.
Pages are pre-built at deploy time and served from Vercel’s global edge network—so the browser gets a finished document from a location near the visitor, not a server assembling the page on the fly.
Next.js compiles and code-splits each page so visitors only load what they need. React updates only what changed without reloading the whole document. Tailwind ships only the CSS classes in use. PostgreSQL, when data is needed, handles queries efficiently over a secure server route—never from the browser directly.
There is no public admin login, no plugin runtime, and no live database behind static pages. The attack surfaces that make WordPress sites common targets simply are not present in this build.
Private work—editing, deploying, secrets—lives in authenticated developer tooling (Cursor, Git, Vercel environment variables), not in a browser-facing login form. HTTPS and edge delivery are on by default from the first deploy.
The site is code-first: layouts, integrations, and experiments are implemented in the project itself, not constrained by what a theme vendor chose to support.
New AI providers, third-party APIs, and product features all follow the same path: write the code, review it, deploy it—no plugin marketplace, no theme ceiling.
Cursor’s AI has full context on the project. Smart UI, automation hooks, and model integrations can go from idea to working code in days—because the model understands the existing codebase and writes code that fits it.
The developer reviews, tests, and ships through the normal Git and Vercel workflow. AI compresses the drafting phase; quality judgment stays constant.
Every deploy is a clean build from a specific Git commit—no server drifting under manual edits. Branches get their own preview URL, making alpha and beta testing free of staging infrastructure.
From ‘should we build this?’ to ‘someone is trying it in a browser’ is minutes. If something goes wrong in production, the previous deploy is one click away in Vercel.
WordPress powers 43% of the web—and for good reason. It's proven, familiar, and has a massive ecosystem. We still build WordPress sites when it makes sense.
But for businesses that need speed, security, and AI-ready architecture, Next.js is the clear choice. Here's why:
Eight questions. No email required.
Get an honest answer about whether a Next.js site fits where your business is right now.
Want a mission-focused site built on the same kind of modern stack? Explore the full service offering.