Going live — Denzel Next.js
Before the Denzel site goes public, replace the demo’s content and point the newsletter box at you; then deploy it to any Next.js host and check it again.
Replacing the demo’s content means the site’s name, the posts, the categories, the authors, the photos and the picks of Home and the sidebar; pointing the newsletter box 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, meta in src/content/pages/home.ts and blog.ts; the share image’s description, shareImage.alt, in src/lib/meta.ts |
| Your name instead of “Denzel”: the breadcrumbs, the page descriptions, the copyright line (“Theme by Marcframe”) | Search src/ for “Denzel” (Editing the content) |
The footer’s text and e-mail (hello@example.com is a placeholder) |
footer in src/content/site.ts |
| The subscriber count of the newsletter box (“Join 89,000 subscribers!”) | footer.newsletter.text in src/content/site.ts |
| Social links (they open the networks’ home pages), and the authors’ | socials in src/content/site.ts; social of each author in src/content/collections/authors.ts |
| Your posts, categories and authors (the demo’s are samples) | src/content/collections/ (Editing the content) |
| Home’s picks, the sidebar’s Recent and Explore Topics, the footer’s two posts | slider, picks, trending in home.ts; sidebar and footer.posts in site.ts (Editing the content) |
| The menu’s categories and its “Author” link | navigation in src/content/site.ts |
| The default category and author (“Uncategory”, “Admin”) kept or deleted | categories.ts, authors.ts |
| A privacy policy for the note under the newsletter box | Forms |
| 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 |
| Placeholder photos replaced (posts, categories, authors, the 404 illustration, the About box’s background) | public/images/ |
| The newsletter box 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 “Denzel”, the sample e-mail, the sample posts and authors or the subscriber count 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 newsletter box, 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.
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.
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 on a phone, and the search (type a word, use the arrow keys, press Escape);
- the slider stepping on Home, Editor’s Pick, Trending and Latest;
- Blog, a category, an author and a post, with its Related Posts and More Articles by;
- the newsletter box.
- Sign up from the live footer with your own address and check that it arrived.
- 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.tswith today’s date, and its photo inpublic/images/; it shows first on Blog, Latest and its category and author pages by itself. 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 post, category and author;
- 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 1600 px wide for the post photos, 800 px for the category photos); the placeholders show the size of each
demo photo. next/image then serves each visitor a scaled, compressed copy.