Going live — Catchup HTML
Publishing the Catchup 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.
Before you upload
Section titled “Before you upload”| Where | |
|---|---|
| Demo domain replaced by yours | Every .html file, sitemap.xml, robots.txt: find https://catchup-html-erapee.vercel.app (Editing the site) |
| Your studio’s name instead of “Catchup”: titles, share tags, the footer note, the logo’s name, the form’s subject | Search the folder for “Catchup” |
Contact details (hello@example.com, the phone number and the Brooklyn address are placeholders) |
The footer of every page, contact.html |
Your booking link (“Book a 15-min call” opens https://cal.com/) |
The footer of every page, every service page |
| Social links (they open the networks’ home pages) and the team’s handles | The footer, Contact, About |
| The line beside the logo in the footer | Every page |
| Titles and descriptions written for your studio | Each page’s <head> |
| Logo, client logos, icons and share image replaced | The logo <svg> (Making it look like your brand), assets/images/logo-*.svg, 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: brands, years, engagement, rating, projects | Home, About (Editing the site) |
Your own awards and team, or the sections removed (the demo’s awards link to https://www.awwwards.com/) |
about.html |
| Testimonials from your own clients | Home, every project page, every service page (Editing the site) |
| Your projects, services, prices 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 (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 “Catchup”, 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 “Catchup”, “example.com”, “555-0123”, “cal.com” and “awwwards” one last time.
What to upload
Section titled “What to upload”Everything except the tools and the documentation:
| Upload | Leave out |
|---|---|
The .html pages, work/, service/, blog/, legal/ |
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.
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, work/liva-beauty-skincare.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 post’s file name holds brackets, blog/5-common-web-design-mistakes-(and-how-to-avoid-them).html, as the demo’s
address does. Every host above serves it, but if you rename the post, a plain name (5-common-web-design-mistakes.html)
is easier to share; change its links and its line in sitemap.xml with it.
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 intro and the hero on Home (open it in a private window to see the intro again), the header coming back after the hero, and the phone menu;
- the logo row, the faces, the testimonial rows and the carousel, and the numbers counting up;
- a project page, a service page and its Per Project / Per Month switch;
- 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).
- 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 post 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 work current. Add projects and posts 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 posts the Blog shows later included);
- one
<h1>per page, and a title and description for every page; - canonical links,
sitemap.xml,robots.txtand 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 the Home hero alone holds four full-screen photos. 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 hero, About, the projects, the services and the posts) matter most on phones.