Skip to content
Sign inJoin waitlist

Compose Digi documentation — HTML

Everything you need to go from the downloaded HTML folder to a published website for your digital marketing agency or studio, in the order to read it.

Guide What it covers
Editing the site Opening the site, editing text, links and images, the sections that repeat, adding and removing services, projects, posts, job openings 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 style guide, the cursor and motion
Forms Making the contact 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 contact details, 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 “Compose” to put your own name in the copy.
  4. Replace the photos in assets/images/: keep the file names and every page picks them up (Editing the site), the client logos, and the About video (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. Upload the folder to your host (Going live).
  • One HTML file per page. about.html is /about.html; each service, project, job opening and post has its own file in services/, projects/, careers/ and blog/ (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 cursor, the tickers, the service list, the plan switch, the process chart, the testimonial slider, the video, the team, “Load More”, the scroll effects, 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 header, the footer with its ticker of service names, the service cards, the project cards, the post cards, the page headers’ social buttons) is written into each of them. 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 posts or case studies every week, choose the Compose Digi Astro or Compose Digi Next.js edition instead: a new post is one entry in a data file, and every page, list and sitemap line follows (Editing without touching HTML).