Skip to content
Sign inJoin waitlist

Going live — Marai Neesu Next.js

Before the Marai Neesu site goes public, replace the demo’s person, links and photos with yours and point the forms at you; then deploy it to any Next.js host and check it again.

Replacing the demo means its name, e-mail, social links, projects, products and photos; pointing the forms at you means giving both 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, city and photo in the logo and on the CV person in src/content/site.ts
Your name instead of “Marai Neesu” and your city instead of “Dubai”: the copy, the testimonials’ quotes, the page descriptions, the alt texts Search src/content/ for “Neesu” and “Dubai” (Editing the content)
Your e-mail (hello@example.com is a placeholder, written twice) contact.email and footer.reach in src/content/site.ts
The footer’s city and its time zone (the clock shows Dubai’s time) footer.city and footer.timeZone in src/content/site.ts
Social and profile links (they open the networks’ home pages) footer.reach and footer.profiles in src/content/site.ts, src/content/collections/socials.ts, the CV’s contact links in src/content/pages/cv.ts
Links that lead to example.com or to a service’s home page: the products’ buy and demo links, the experiences, the services’ “More Details” (https://contra.com/), the course’s “Free Preview” lessons and “Enroll Today”, the CV’s education and certifications src/content/collections/products.ts, experiences.ts, services.ts; src/content/pages/courses.ts and cv.ts
Browser icons replaced src/app/icon.png, src/app/apple-icon.png
Share image replaced and described public/opengraph-image.png, its description in src/lib/meta.ts
Demo photos and screenshots replaced (the download has placeholders) public/images/
Client logos replaced (the samples are Logoipsum placeholders) public/images/client-*.svg, projectsPage.clients in src/content/pages/projects.ts
Your own projects, products, posts, services, testimonials, experiences and tools src/content/collections/
The course: yours, or the page removed src/content/pages/courses.ts (Pages and sections)
Page titles and descriptions written for your work The meta of each file in src/content/pages/
Both 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 “Marai Neesu”, the sample e-mail, the testimonials, the example links, the course or the sample client logos on a live site is the most common mistake. The demo’s six products and six projects are real templates by Marcframe, shown as examples: replace them with your own work.

The site is a normal Next.js app: it builds to pre-rendered pages and runs on Node.js, which also handles the two 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, and on desktop the header stepping aside as you scroll down and coming back as you scroll up;
    • the hovers: the e-mail of the Home hero, the service cards’ rolling photos, the logo’s “Back to Homepage”;
    • the testimonials (a slideshow on phones), the client logos, the questions and the course modules;
    • “Load More” on the Blog, and Go Back on a project, product and post page;
    • the footer’s clock and both forms.
  2. Send yourself an inquiry from the Contact page and sign up to the newsletter on the live site, and reply to the test.
  3. 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.
  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 project one entry in projects.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 posts behind “Load More” 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. Export photos at the size they are shown, not the size your camera produced; the placeholders show the size each one was designed for.