Skip to content
Sign inJoin waitlist

Going live — Semono Next.js

Before the Semono 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 its name, details, figures, photos and videos; pointing the forms at you means giving all three 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: write yours) site in src/content/site.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts
Your firm’s name instead of “Semono”: the copy, the footer, the testimonials’ quotes, the posts, the careers and the legal texts Search src/content/ for “Semono” (Editing the content)
Contact details (hello@example.com, the phone number and the address are placeholders) contact in src/content/site.ts
Business hours info.hours in src/content/pages/contact.ts
Your booking link (“Book a free consultation” on Home opens https://cal.com/) process.book in src/content/pages/home.ts
Social links and the team’s LinkedIn links (they open the networks’ home pages) footer.socials in src/content/site.ts; linkedin of each member in src/content/collections/team.ts
The line about the firm and the taglines in the footer footer in src/content/site.ts
Logo replaced src/design-system/components/brand/Logo.tsx (Making it look like your brand)
Browser icons replaced src/app/icon.svg, src/app/apple-icon.png
Share image replaced and described public/opengraph-image.png, its description in src/lib/meta.ts
Demo photos, portraits and client logos replaced public/images/
The two videos and their posters replaced (or removed) Editing the content
Your own figures: projects, partners, satisfaction, reach facts in src/content/pages/home.ts (About shows the same four)
Testimonials from your own clients, with their logos and results src/content/collections/testimonials.ts
Your services, team, posts and open positions src/content/collections/
Legal texts of your own (the demo’s Privacy Policy and Terms of Service are samples) src/content/collections/legal.ts
Page titles and descriptions written for your work The meta of each file in src/content/pages/
The Contact form’s service choices match your services contactForm.fields.service.options in src/content/pages/contact.ts
The three 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 “Semono”, the sample e-mail, the sample figures, the testimonials, the legal texts, the stock videos or the sample client logos 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 three 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.

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, the phone menu, the header over the Home photo that turns light at “About Semono”, and the page change when you follow a link;
    • the accordion of “Why Choose”, the process tabs and the questions of Contact;
    • Services, Testimonial and Blog loading more as you scroll;
    • a service page and a career page, each with its form;
    • the two videos, which should play when pressed;
    • the Contact form.
  2. Send yourself an enquiry from each of the three forms on the live site and reply to it.
  3. Verify the share card. Paste the URL of the home page and of a service 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 in src/content/collections/posts.ts (at the top of the list), a new position one entry in careers.ts; 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 rows of Services and Testimonial and the later cards of the Blog 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.

Keeping the site fast is mostly about images and videos. Export photos at the size they are shown, not the size your camera produced; the placeholders show the size each one was designed for. Keep your videos short and small, because they loop: a clip is only fetched when a visitor presses play, so it costs nothing until then. The demo’s clips play from a stock site whose servers set cookies of their own; your own video files from your own domain don’t.