Skip to content
Sign inJoin waitlist

Going live — Cerette HTML

Publishing the Cerette HTML edition means replacing the demo’s details, pictures and video, 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://cerette-html-erapee.vercel.app (Editing the site)
Your studio’s name instead of “Cerette”: titles, share tags, the footer note, the logo’s name, the forms’ subjects, the copy Search the folder for “Cerette”
Contact details (hello@example.com, +1 (000) 123-4567 and the Madison Avenue address are placeholders), the working hours The footer of every page, contact.html
Your booking link (“Book a call” and “Schedule Consultation” open https://cal.com/) Home, About, Projects, Services, every project and every post
Social links (they open the networks’ home pages) The footer of every page
The line under the logo in the footer Every page
Titles and descriptions written for your studio Each page’s <head>
Logo, icons and share image replaced The logo <svg> (Making it look like your brand), icon.svg, 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 hero video (the demo’s clip plays from Pexels’ servers) index.html (Editing the site)
Your own figures, awards and founder’s quote, or the sections removed Home, About, Services
Testimonials from your own clients Home, Projects
Your team about.html (Editing the site)
Your projects, services and posts The pages and their lists (Editing the site)
Legal pages written for your studio legal/ (Editing the site)
The form delivers to you, with your name in its subject assets/js/config.js, contact.html, service.html, service/ (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 “Cerette”, the sample e-mail and phone, the sample figures, the testimonials, the awards or the demo’s video on a live site is the most common mistake: search the folder for “Cerette”, “example.com”, “123-4567”, “cal.com” and “.mp4” (the hero video’s src should point at your own file) one last time.

Everything except the tools and the documentation:

Upload Leave out
The .html pages, project/, service/, blog/, legal/ node_modules/, src/, docs/
assets/ package.json, package-lock.json
icon.svg, 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, project/aureline-house.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/studio/, or a GitHub Pages project site), add that folder to those paths.

One project’s file name holds an accented letter, project/elvaré-studio.html, as the demo’s address does. Every host above serves it, but if you rename the project, a plain name (elvare-studio.html) is easier to share and type; change its links and its line in sitemap.xml with it.

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 hero video and its text on Home, the header turning from transparent to cream, and the phone menu;
    • the services switcher on a desktop, a tablet and a phone;
    • About’s team picker and, on a phone, its grid loading more people;
    • a project page with its sticky photos, a service page and its form;
    • the Blog loading more posts as you scroll, and a post;
    • the hovers on the buttons, the cards and the footer’s links;
    • the 404 page (open an address that doesn’t exist).
  2. Send yourself a test from the forms and reply to it.
  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. 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 and posts 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 posts the Blog shows later included);
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards, posts as articles; 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, and Home opens with a video. Keep the site fast by exporting photos at the size they are shown and compressing them, and the video to a few MB; the photos at the top of each page (About, the projects, the services and the posts) matter most on phones.