Skip to content
Sign inJoin waitlist

Going live — Lookis Next.js

Before the Lookis site goes public, replace the demo’s content and point the form at you; then deploy it to any Next.js host and check it again.

Replacing the demo’s content means the photographer’s name and town, the details, the numbers, the photos and the links; pointing the form at you means giving it 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 name, town and time zone for the header’s clock owner in src/content/site.ts
Your name instead of “Daniel Mercer”, your town instead of Asheville: the copy, the footer, the testimonials, the projects and the services Search src/content/ for “Daniel”, “Mercer” and “Asheville” (Editing the content)
Contact details (hello@example.com and the phone number are placeholders) contact in src/content/site.ts
Your booking link (“Book a session”, “Schedule a call” open https://cal.com/) bookingHref and footer.action in src/content/site.ts, hero.primary in src/content/pages/home.ts
Social links (they open the networks’ home pages) and the Instagram button of “See what I do” socials in src/content/site.ts; showcase.instagram in src/content/pages/shared.ts
Your awards, with links to them (the demo’s link to awwwards.com) awards in src/content/pages/about.ts
Your own numbers: clients, projects, cities, countries facts in src/content/pages/home.ts and in about.ts (two copies)
Testimonials from your own clients testimonials in src/content/pages/shared.ts
Your projects and services, with your prices src/content/collections/
The questions and answers of Services questions in src/content/pages/services.ts
Logo replaced src/design-system/components/brand/Logo.tsx (Making it look like your brand)
Browser icons replaced public/icon-light.png, public/icon-dark.png, 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/
Page titles and descriptions written for your work 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 “Daniel Mercer”, the sample e-mail, the sample numbers, the awards, the testimonials or the booking placeholder 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 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)”
  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 and the clock;
    • the name running across the Home hero and the testimonial slideshow;
    • the Portfolio tabs, and Portfolio loading more as you scroll;
    • a project page and a service page;
    • the questions on Services;
    • the Contact form.
  2. Send yourself an enquiry from the live site and reply to it.
  3. 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.
  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 project is one entry at the top of src/content/collections/portfolio.ts, with its photos 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 projects of Portfolio 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.

Keeping the site fast is mostly about images. A photography site is mostly photos: export them at the size they are shown, not the size your camera produced (about 2400 px wide for the full-width photos, 1440 px for the projects); the placeholders show the size of each demo photo. next/image then serves each visitor a scaled, compressed copy.