Going live — Compose Digi Next.js
Before the Compose Digi site goes public, replace the demo’s content and point the contact form at you; then deploy it to any Next.js host and check it again.
Replacing the demo’s content means the agency’s name, the details, the services and their prices, the projects, the team, the photos, the client logos and the video; pointing the form at you means giving it 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; Home’s description in home.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts |
| Your agency instead of “Compose”, your founder instead of “Davide Gotlieb”: the copy, the quote, the job openings | Search src/content/ for “Compose” (Editing the content) |
Contact details (hello@example.com, the phone number and the address are placeholders) |
contact in src/content/site.ts |
Your booking page instead of https://cal.com/ (“Book a call”) |
bookCallLink and the footer’s “Book a Call” in src/content/site.ts |
| Social links (they open the networks’ home pages): the footer, the page tops and every team member | socials and pageSocials in src/content/site.ts, teamSocials in src/content/pages/about.ts |
| Your own rating and figures (“4.9”, “Trusted by 500+ Brands Globally”, “260+ Campaigns Launched”, …) | hero.rating in home.ts, facts in about.ts |
| Your services and their prices | src/content/collections/services.ts |
Your projects and your clients’ words, your team, your posts and openings (with your own address instead of careers@example.com) |
src/content/collections/, team in about.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 (the demo’s shows an older Compose design) | public/opengraph-image.png, its description in src/lib/meta.ts |
| Placeholder photos replaced, the four faces of the Home rating too | public/images/ |
| The sample client logos replaced | public/images/client-logo-*.svg, facts.logos in about.ts |
| The About video replaced (it plays the original template’s promo from YouTube) | video.youtubeId in src/content/pages/about.ts (Editing the content) |
| Page titles and descriptions written for your agency | The meta of each file in src/content/pages/ |
| The form delivers 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 “Compose”, the sample e-mail and address, the sample prices, the figures, the client quotes or the promo video 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 contact form, so any host that supports Next.js works. It can’t be published as plain static files, because the form needs 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 custom cursor;
- the moving strips (Home, About, the footer);
- the service list on Home, a service page with its Weekly / Monthly switch, the Services testimonials and process chart;
- a project page while scrolling, Projects, Blog and Careers with “Load More”, a post with Prev and Next, a job opening;
- the About video;
- the contact form.
- Send yourself a message from the live site and reply to it.
- Verify the share card. Paste the URL of the home page and of a project 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 at the top of
src/content/collections/posts.ts, with its photo inpublic/images/; a new case study one entry inprojects.ts; 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 projects, posts and openings behind “Load More” 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 that says something.
Keeping the site fast is mostly about images. Export photos at the size they are shown, not the size your camera produced
(about 2000–2400 px wide for the full-width photos and the covers); the placeholders show the size of each demo photo.
next/image then serves each visitor a scaled, compressed copy. The About video loads from YouTube only when the
visitor presses Play.