Our own website runs on a headless CMS we built: a Laravel admin that owns every page, case study, blog post and SEO field, and a Next.js frontend that reads it all through an API.
The project in short
Nexaces.com is our own website, and it runs on a headless CMS we designed and built. A Laravel admin holds every page, service, case study, blog post and SEO field. A Next.js frontend reads that content through an API and serves it as fast, pre-rendered pages.
It is the setup we offer agencies: content managed in one place by the people who own it, a frontend that stays fast and accessible, and no developer needed to change a sentence.
What we were solving
A firm that sells web work to agencies gets judged on its own site first. It had to be fast, accessible and easy to keep current, and keeping it current could not mean a code change and a deploy every time a sentence, a certificate number or a case study changed.
What we set out to do
- Every piece of public content editable from an admin, with no developer in the loop
- One place for SEO: titles, descriptions, social images, permalinks and the sitemap
- Pages served as static HTML for speed, refreshing themselves after an edit
- The same backend running the business: contracting data, clients, documents and finances
What we built
A Laravel application is the single source of truth. Its admin manages the home page, services, case studies, blog, FAQs, testimonials, page banners, legal pages and the capabilities record that prime contractors read. A Next.js frontend pulls that content through a REST API and renders it as static pages that regenerate in the background, so an edit appears on the live site within the hour without a rebuild.
Because the admin already held the content, it grew into the back office too: client records, document templates with e-signing, and earnings and expenses with Stripe sync, all behind the same login.
What it does
- Content editing for every public section of the site, including per-page SEO and social images
- One permalink list covering services, posts, case studies and experience pages
- Sitemap generated from the admin
- Founder experience section with attribution rules enforced in the data model, not by hand
- Capabilities record that also feeds a one-page PDF capability statement
- Clients, documents with e-signing, and finance in the same admin
How we built it
The API is Laravel on PHP 8, with public endpoints behind an API key and rate limiting (read-only apart from the contact form), and every content change kept behind the admin login. The frontend is Next.js and React with incremental static regeneration, so visitors get pre-rendered HTML and the API is only asked for fresh content periodically. Both run on a Linux VPS we manage, alongside our other production products.
Deploys are scripted and guarded: a database and file backup first, a dry run that lists what will change, an uptime check after release, and only the one application restarted, so the other products on the server are never touched.
Where it stands now
A content change is an admin edit, not a code change and a deploy. The same pattern (a Laravel API behind a Next.js frontend) runs our other products, Fictbase's licensing service and Doodrio's app, which is why we offer it to agencies as a headless setup: one backend that can serve more than one site, so a change is made once.