Skip to content
Sign inJoin waitlist

Cerette documentation — HTML

Everything you need to go from the downloaded folder to a published architecture or interior design studio site. Read in this order, or jump to what you need.

Guide What it covers
Editing the site Opening the site, editing text, links, images and the hero video, the sections that repeat, the services switcher, the team, adding and removing projects, services, posts and pages
Pages and sections Every kind of page, its sections, where its text and photos are, and how the pages link to each other
Making it look like your brand Colours, the logo, the fonts, the Tailwind classes, rebuilding the stylesheet, the header, the style guide and motion
Forms Making the inquiry form deliver to you
Editing without touching HTML Your options when someone else needs to edit the site without touching HTML
Going live Pre-launch checklist, uploading, domains, what to do after launch
Troubleshooting and questions Errors, questions and answers
  1. Open index.html in your browser. That is the whole site: no install, no build.
  2. Open the folder in a code editor (VS Code is a good free one).
  3. Replace the e-mail, the phone, the social links, the booking link and the demo domain across all files with your editor’s find and replace in files (Editing the site), then search for “Cerette” to put your own studio’s name in the titles, the footer and the copy.
  4. Replace the photos in assets/images/ (keep the file names and every page picks them up) and the Home hero video (Editing the site, Editing the site).
  5. Replace the logo (Making it look like your brand), the icons and the share image in the root folder (icon.svg, apple-icon.png, opengraph-image.png).
  6. Put your form endpoint in assets/js/config.js (Forms).
  7. Have your own legal pages written, then upload the folder to your host (Going live).
  • One HTML file per page. about.html is /about.html; each project, service, post and legal page has its own file in project/, service/, blog/ and legal/ (Pages and sections).
  • One stylesheet. assets/css/style.css, built from src/css/style.css with Tailwind CSS. You only rebuild it when you use a class that isn’t in the site yet, or change the theme (Making it look like your brand).
  • One script. assets/js/main.js runs the header and the phone menu, the text and block effects, the services switcher, the team picker, the loading on scroll, the form and the hovers. You rarely need to touch it: your settings go in assets/js/config.js.
  • Copies, not references. A block that shows on several pages (the project cards, the services, the testimonials, the post cards, the call to action, the footer) is written into each of them, and some are written more than once on the same page, once per screen size. Change every copy, or use find and replace in files (Editing the site).
  • No framework, no dependencies at runtime. The pages work from any static host, and even straight from disk.

If you will publish a post every week, choose the Cerette Astro or Cerette Next.js edition instead: a new post is one entry in a data file, and every list, page and sitemap line follows (Editing without touching HTML).