Skip to content
Sign inJoin waitlist

Going live — Lookis HTML

Publishing the Lookis HTML edition means replacing the demo’s details and pictures, pointing the form at you and uploading the folder to any static host.

There is no build command and no server software: the folder you edited is the site.

Where
Demo domain replaced by yours Every .html file, sitemap.xml, robots.txt: find https://lookis-html-templategum.vercel.app (Editing the site)
Your name instead of “Daniel Mercer”: the hero and its ticker, the copy, the testimonials’ quotes, the footer note Search the folder for “Daniel”
Your place and time zone in the header “Asheville, (NC)” and America/New_York (Editing the site)
Contact details (hello@example.com and the phone number are placeholders) The footer of every page
Your booking link (“Book a session” and “Schedule a call” open https://cal.com/) Every page
Social links and the Instagram handle (they open the networks’ home pages) The footer, the Home hero, About, Contact, “See what I do”
The line under “Let’s Connect” in the footer Every page
Titles and descriptions written for your work Each page’s <head>; Home’s title still names the template
Logo, icons and share image replaced The logo <svg> in every page (Making it look like your brand), icon-light.png, icon-dark.png, apple-icon.png, opengraph-image.png (2400 × 1260; 1200 × 630 or larger) and its description, og:image:alt
Demo photos and portraits replaced assets/images/ (Editing the site)
Your own numbers: clients, projects, cities, countries Home, About
Your own awards, or the section removed (the demo’s link to https://www.awwwards.com/) about.html
Testimonials from your own clients Home, Services, every service page (Editing the site)
Your projects and services, with your prices and answers The pages and their lists (Editing the site)
The form delivers to you, with your name in its subject assets/js/config.js, contact.html (Forms)
Style guide kept or deleted style-guide.html
Stylesheet rebuilt if you changed the theme or used new classes npm run build:css (Making it look like your brand)

Leaving “Daniel Mercer”, the sample e-mail, the sample numbers, the testimonials or the awards on a live site is the most common mistake: search the folder for “Daniel”, “Asheville”, “example.com” and “awwwards” one last time.

Everything except the tools and the documentation:

Upload Leave out
The .html pages, portfolio/, services/ node_modules/, src/, docs/
assets/ package.json, package-lock.json
icon-light.png, icon-dark.png, apple-icon.png, opengraph-image.png README.md, CHANGELOG.md, LICENSE.md
sitemap.xml, robots.txt Documentation.html, Documentation.pdf

Uploading the extra files does no harm, but there is no reason to publish them.

Host How
Netlify Drag the folder onto Netlify Drop. Done; then add your domain.
Cloudflare Pages, Vercel Upload the folder or connect a Git repository; no build command, the output folder is the root.
GitHub Pages Push the folder to a repository and enable Pages.
Shared hosting (cPanel, Plesk…) Upload through the file manager or FTP into public_html (or www).

Pages link to each other with their file names (about.html, portfolio/downtown-vows.html), so no server configuration is needed. Most hosts serve 404.html for unknown addresses automatically; on Apache, add ErrorDocument 404 /404.html to .htaccess. The paths in 404.html start at the site’s root (/assets/css/style.css, /index.html), because hosts show it at any address: if your site lives in a sub-folder of its domain (example.com/photos/, or a GitHub Pages project site), add that folder to those paths.

Add it in the host’s domain settings and point your DNS where they tell you (usually an A record or a CNAME). Turn on HTTPS: every host above does it for free.

  1. Check the pages. Click through every page on a phone and a laptop:
    • the name ticker and the introduction on Home, the clock in the header, and the phone menu;
    • the testimonial slideshow and its arrows;
    • the Portfolio tabs, and the list loading more as you scroll;
    • a project page, a service page and the questions on Services;
    • the hovers on the project cards, the service rows and the gallery;
    • the 404 page (open an address that doesn’t exist).
  2. Send yourself a test from the contact form 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. Paste your snippet before </head> in every page (find and replace on </head> does it at once), or use your host’s built-in analytics (Cloudflare Web Analytics, Plausible, Fathom). None of them need a cookie banner.
  6. Keep the work current. Add projects as described in Editing the site, and keep sitemap.xml in step.

The pages ship with what search engines look for:

  • real HTML, with links in it to every page (the projects Portfolio shows later included);
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards; the 404 page and the style guide are kept out of search results (noindex);
  • lazy-loaded images below the top of each page, with their size written so that they keep their space while they load.

Each image is one file, used at every screen size. A photography site lives on its photos, so keep it fast by exporting them at the size they are shown and compressing them; the photos at the top of each page (the Home hero and the large photo of About, Services, the projects, the services and Contact) matter most on phones.