Going live — Cerette Next.js
Before the Cerette site goes public, replace the demo’s content and point the forms at you; then deploy it to any Next.js host and check it again.
Replacing the demo’s content means the studio’s name, the details, the numbers, the photos, the video, the people and the links; pointing the forms at you means giving them a destination. Once the site is deployed, click through the live address once more.
Before you deploy
Section titled “Before you deploy”| Where | |
|---|---|
Your domain in site.url (until you change it, it is the demo’s address) |
src/content/site.ts. Share links, sitemap.xml and robots.txt are built from it. |
| Name, title and description (they describe the template: write yours) | site in src/content/site.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts |
| Your studio’s name instead of “Cerette”: the copy, the founder’s quote, the testimonials, the forms’ titles, the footer’s copyright, the legal pages | Search src/content/ for “Cerette” (Editing the content) |
Contact details (hello@example.com, the phone number, the New York address and the hours are placeholders) |
contact in src/content/site.ts; address and hours in src/content/pages/contact.ts |
Your booking link (“Book a call” and “Schedule Consultation” open https://cal.com/) |
bookingHref in src/content/site.ts |
| Social links (they open the networks’ home pages) | socials in src/content/site.ts |
| Your own hero video (the demo’s is streamed from another server and is not yours to use) and its poster | home.hero.video in src/content/pages/home.ts (Editing the content) |
| Your own numbers, awards and founder’s quote | about, achievement and quote in src/content/pages/home.ts (About and Services show them too) |
| The years beside the Projects title (“(2005 - 2026)”) | projectsPage.title.aside in src/content/pages/projects.ts |
| Your projects, services, testimonials from your own clients, your team, your posts | src/content/collections/ |
| Your own Privacy Policy and Terms of Service (the demo’s are sample text) | src/content/collections/legal.ts |
| Logo replaced | src/design-system/components/brand/Logo.tsx (Making it look like your brand) |
| Browser icons replaced | public/icon.svg, src/app/apple-icon.png |
| Share image replaced and described | public/opengraph-image.png, its description in src/lib/meta.ts |
| Placeholder photos replaced | public/images/ |
| Page titles and descriptions written for your work | The meta of each file in src/content/pages/ |
| The forms deliver to you, and ask for what you need (only the drop-downs are required as shipped) | Forms |
| Style guide kept or deleted | src/app/style-guide/ |
npm run lint and npm run build pass |
— |
The demo content is there to be replaced. Leaving “Cerette”, the sample e-mail, phone and address, the sample numbers, the awards, the team, the testimonials, the hero video or the booking placeholder on a live site is the most common mistake.
Deploy
Section titled “Deploy”The site is a normal Next.js app: it builds to pre-rendered pages and runs on Node.js, which also handles the inquiry forms, so any host that supports Next.js works. It can’t be published as plain static files, because the forms need the server.
Vercel (made by the Next.js team, free for personal sites)
Section titled “Vercel (made by the Next.js team, free for personal sites)”- Push the project to GitHub, GitLab or Bitbucket.
- https://vercel.com/new → import the repository → Deploy. The framework, build command and output are detected.
- Add your form variables under Settings → Environment Variables, then redeploy.
- Settings → Domains → add your domain and follow the DNS instructions.
Netlify
Section titled “Netlify”Import the repository, keep the detected settings (npm run build), add the environment variables, deploy.
Cloudflare
Section titled “Cloudflare”Cloudflare runs Next.js through the OpenNext adapter (@opennextjs/cloudflare); follow Cloudflare’s Next.js guide to
build and deploy with Wrangler.
Your own server
Section titled “Your own server”npm cinpm run buildnpm start # listens on port 3000Run it under a process manager (pm2, systemd) behind nginx or Caddy for TLS, or in a container: an LTS Node image such
as node:24-alpine, copy the project, build, CMD ["npm", "start"].
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the menu, the phone menu, and the header on Home and on a project page as you scroll past the cover;
- the hero’s video and its title appearing letter by letter;
- the services on Home (click the names; on a phone, open the rows) and the team on About (point at the names on a laptop; scroll the cards on a phone);
- a project page, a service page with its form, and a post;
- Blog loading more posts as you scroll;
- the Contact form.
- Send yourself an inquiry from the live site, from Contact and from a service’s page, and reply to it.
- Verify the share card. Paste the URL of the home page and of a post into https://www.opengraph.xyz or a chat window, and confirm the image and title.
- Tell Google. Add the site to Search Console, verify ownership and
submit
https://yourdomain.com/sitemap.xml. Bing has the same thing in Webmaster Tools. - Analytics, if you want it. Add your snippet to
src/app/layout.tsx, or use your host’s built-in analytics (Vercel Analytics, Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner. - Keep it current. A new post is one entry in
src/content/collections/posts.ts, with its photo inpublic/images/; see Editing the content. Connect a CMS (Using a headless CMS) if someone else will publish.
Performance and SEO
Section titled “Performance and SEO”The template ships with what search engines look for:
- pre-rendered HTML, with links in it to every page (the later posts of Blog included);
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards; - sized, lazy-loaded images that keep their space while they load, and alt texts on every photo.
Keeping the site fast is mostly about images and the video: export photos at the size they are shown, not the size your
camera produced (about 2400 px wide for the full-width photos, 1100 to 1700 px for the half-width ones); the
placeholders show the size of each demo photo. next/image then serves each visitor a scaled, compressed copy. Keep the
hero video short and small, since every visitor to Home loads it.