Going live — Kendi Next.js
Before the Kendi site goes public, replace the demo’s magazine with yours, fill in the legal pages and point the forms at you; then deploy it to any Next.js host and check it again.
Replacing the demo’s magazine means its name, contact details, posts, authors, team, photos and the sample ad; pointing the forms at you means giving the newsletter and the contact form 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 magazine’s name instead of “Kendi”: the copyright, About, Contact, the page titles and descriptions | Search src/content/ (Editing the content) |
| Contact details: the e-mail, phone, address and hours are made up | contact in src/content/site.ts |
| Social links (they open the networks’ home pages), the authors’ links and the footer grid’s links | socials in src/content/site.ts, authors.ts, instagram.ts |
| The sidebar’s About text (“We influence 20 million users…” is the demo’s claim) | sidebar.about in src/content/site.ts |
The legal pages: every placeholder filled in ([Your Company Name], [URL], [Contact Information], [Your Jurisdiction], [Arbitration Location], [Link to Privacy Policy]) and the texts checked for your site |
src/content/collections/legal.ts (Editing the content) |
| The sponsored ad replaced with your own, or removed (Tenq Tech is a made-up advertiser) | sponsoredAd in src/content/site.ts (Editing the content) |
| Your posts, categories and authors | src/content/collections/ |
| Your team on About | src/content/collections/team.ts |
| Logo replaced | public/images/logo.svg (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 replaced | public/images/ |
| Page titles and descriptions written for your site | 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 “Kendi”, the sample e-mail and phone, the demo posts and authors, the sample ad or the legal placeholders 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 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 Categories menu on desktop, the tablet and phone menus;
- the hero slideshow and the Inspiration carousel;
- Articles loading more posts as you scroll;
- a post with its sidebar and Related Post, a category page, an author page;
- the ad’s button, the footer’s links and legal pages.
- Sign up and write to yourself on the live site — the newsletter from Home, the sidebar and the band, and a contact message — and reply to the message.
- 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 publishing. A new post is one entry in
src/content/collections/posts.ts(its date puts it in place); see Editing the content. Connect a CMS (Using a headless CMS) if writers who don’t use a code editor 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 — every post of Articles too, even the ones that load on scroll;
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand share cards (posts as articles, with their date); - sized, lazy-loaded images that keep their space while they load.
Keeping the site fast is mostly about images. Export photos at the size they are shown, not the size your camera produced; the placeholders show the size each one was designed for.