Going live — Compose Digi HTML
Publishing Compose Digi’s HTML edition means replacing the demo’s details, pictures, logos and video, pointing the contact form at you and uploading the folder to a host.
There is no build command and no server software: the folder you edited is the site.
Before you upload
Section titled “Before you upload”| Where | |
|---|---|
| Demo domain replaced by yours | Every .html file, sitemap.xml, robots.txt: find https://compose-digi-html-marcframe.vercel.app (Editing the site) |
| Your name instead of “Compose”: the logo’s name, the titles, the copy (“At Compose, …”), the founder’s quote and its signature, the call to action, the job openings | Search the folder for “Compose” and “Davide” |
Contact details (hello@example.com, careers@example.com, the phone number and the Wonderland address are placeholders) |
The footer of every page; the hiring e-mail on every job opening |
Your booking page instead of https://cal.com/ |
“Book a call” on Home, “Book a Call” in the footer |
| Social links (they open the networks’ home pages) | The footer, the page headers’ buttons, the team on About |
| Titles and descriptions written for your agency | Each page’s <head>; Home’s description still promises “higher ROI” |
| Logo, icons and share image replaced | The logo <svg> in every page (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. The demo’s share image is the Framer template’s and shows an old sample e-mail: replace it |
| Demo photos and portraits replaced | assets/images/ (Editing the site) |
| The client logos replaced by your clients’ (with their permission) or removed | about.html (Editing the site) |
| The About video replaced (the demo plays the Framer template’s promotional film from YouTube) | about.html (Editing the site) |
| Your services, plans and prices | Home, Services, services/ (Editing the site) |
| Your own projects and client quotes, with your clients’ consent | Home, Projects, projects/, the Services slider |
| Your own figures and rating (“4.9 / 5.0”, “500+”, “260+”, “5x”, “10M+”, “98%”) | Home, About (Editing the site) |
Your team and your open positions, or the demo’s removed (several hold […] placeholders) |
About, Careers, careers/ (Editing the site) |
| Your posts, or the demo’s removed | blog/, the Blog page, Home (Editing the site) |
| A privacy policy, if your country expects one for the contact form | A page of your own (Forms) |
The form delivers to you, with your wording 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 “Compose”, the sample e-mails, the sample figures, the client logos or the demo’s video on a live site is the most common mistake: search the folder for “Compose”, “example.com”, “Wonderland”, “cal.com”, “youtube” and “[” one last time.
What to upload
Section titled “What to upload”Everything except the tools and the documentation:
| Upload | Leave out |
|---|---|
The .html pages, services/, projects/, careers/, blog/ |
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.
Where to host
Section titled “Where to host”| 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, projects/elevating-education-through-digital-marketing.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/agency/, or a GitHub Pages project site), add that folder to those paths.
One demo file name has an accented letter: projects/digital-strategy-for-a-leading-home-décor-brand.html. Browsers and
the hosts above handle it, but some FTP programs and zip tools change such names. If that project’s page answers “not
found” after uploading, rename the file without the accent (…-home-decor-brand.html) and replace the old name in every
page and in sitemap.xml (where it is written home-d%C3%A9cor).
Your domain
Section titled “Your domain”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.
After it is live
Section titled “After it is live”- Check the pages. Click through every page on a phone and a laptop:
- the Home ticker, the service list opening one row at a time, the phone menu;
- the cursor over the photos and cards (on a laptop with a mouse);
- the Weekly / Monthly switch on a service page, the process chart and the testimonial slider on Services;
- the scroll effects of a project page;
- your video on About;
- “Load More” on Projects, Careers and Blog, a post with its Prev and Next, a job opening;
- the 404 page (open an address that doesn’t exist).
- Send yourself a test from the contact form and reply to it.
- 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.
- 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. - 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. - Keep the blog and the case studies current. Add posts and projects as described in
Editing the site, and keep
sitemap.xmlin step.
Performance and SEO
Section titled “Performance and SEO”The pages ship with what search engines look for:
- real HTML, with links in it to every page (the cards “Load More” shows later included);
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand 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; the video loads only when the visitor presses Play.
Each image is one file, used at every screen size. Keep the site fast by exporting photos at the size they are shown and compressing them; the photos at the top of each page (the Home ticker’s covers, a project’s cover and a post’s cover) matter most on phones.