Skip to content
Sign inJoin waitlist

Going live — Balancee Next.js

Before the Balancee 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 company’s name, the details, the services, the case studies, the figures, the team, the photos, the videos and the legal texts; pointing the forms at you means giving them a destination. Once the site is deployed, click through the live address once more.

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, and the title is Home’s title: write yours) site in src/content/site.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts
Your company instead of “Balancee”, your authors instead of the team members’ names (Emma Carter, Daniel Brooks …), your address instead of Brooklyn: the copy, the footer, the posts, the testimonials, the legal pages Search src/content/ for “Balancee”, the team members’ names and “Brooklyn” (Editing the content)
Contact details (hello@example.com, the phone number, the address and the hours are placeholders) contact in src/content/site.ts
Social links (they open the networks’ home pages) socials in src/content/site.ts; the team’s LinkedIn links in team.members of about.ts
Where “Let’s talk” and “Book a Free Consultation” lead (the demo: the home page of cal.com) bookingLink in src/content/site.ts
Your own figures and rating (“$86M+”, “320+”, “4.9/5.0 … 40+ global clients”, the case studies’ results) home.ts, about.ts, src/content/collections/portfolio.ts
The awards (their links open awwwards.com) and the timeline journey in src/content/pages/about.ts
Your testimonials, client logos and team testimonials and clients in home.ts, team in about.ts
Your services, case studies and posts (and Home’s six case study slugs) src/content/collections/, caseStudies in home.ts (Editing the content)
The contact form’s service choices contactForm in src/content/pages/shared.ts
Legal pages written for your company ([Your Company Name], [URL] and the sample text) src/content/collections/legal.ts
Wordmark replaced src/design-system/components/brand/Logo.tsx (Making it look like your brand)
Browser icons replaced (the “B”) public/icon-light.svg, public/icon-dark.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/
The three videos replaced (they play from the Pexels website) hero.video, about.video and testimonials.items in src/content/pages/home.ts (Editing the content)
Page titles and descriptions written for your company The meta of each file in src/content/pages/
The forms deliver to you 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 “Balancee”, the sample e-mail and address, the figures, the client testimonials or the sample legal texts on a live site is the most common mistake.

The site is a normal Next.js app: it builds to pre-rendered pages and runs on Node.js, which also handles the two 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)”
  1. Push the project to GitHub, GitLab or Bitbucket.
  2. https://vercel.com/new → import the repository → Deploy. The framework, build command and output are detected.
  3. Add your form variables under Settings → Environment Variables, then redeploy.
  4. Settings → Domains → add your domain and follow the DNS instructions.

If your folder has a vercel.json with a git entry that switches off automatic deployments (the demo is deployed that way), delete the entry if you want Vercel to deploy on every push.

Import the repository, keep the detected settings (npm run build), add the environment variables, deploy.

Cloudflare runs Next.js through the OpenNext adapter (@opennextjs/cloudflare); follow Cloudflare’s Next.js guide to build and deploy with Wrangler.

Terminal window
npm ci
npm run build
npm start # listens on port 3000

Run 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"].

  1. Check the pages. Click through every page on a phone and a laptop:
    • the menu and the phone menu;
    • the logo loop, the rows of case studies opening, and the three videos;
    • Portfolio and Blog loading more as you scroll, a service, a case study, a post and a legal page;
    • both forms.
  2. Send yourself a message from the live contact form and a subscription from the footer, and reply to the first.
  3. 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.
  4. 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.
  5. 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.
  6. Keep it current. A new post is one entry at the top of src/content/collections/posts.ts, with its photo in public/images/; see Editing the content. Connect a CMS (Using a headless CMS) if someone else will publish.

The template ships with what search engines look for:

  • pre-rendered HTML, with links in it to every page (the later posts and case studies of the lists included);
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards;
  • sized, lazy-loaded images that keep their space while they load, and alt texts on every photo that says something.

Keeping the site fast is mostly about images and videos. Export photos at the size they are shown, not the size your camera produced (about 2400 px wide for the full-width photos, 2000 px for the post covers); the placeholders show the size of each demo photo. next/image then serves each visitor a scaled, compressed copy. Keep each video to a few MB: the hero video starts as soon as the page loads, so it is the one that matters most.