Skip to content
Sign inJoin waitlist

Going live — Balancee HTML

Publishing Balancee’s HTML edition means replacing the demo’s details, pictures and videos, pointing the forms 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.

Where
Demo domain replaced by yours Every .html file, sitemap.xml, robots.txt: find https://balancee-html-framebrick.vercel.app (Editing the site)
Your name instead of “Balancee”: the wordmark, the titles, the About and Home copy, the footer note Search the folder for “Balancee”
Contact details (hello@example.com, the phone number, the Brooklyn address and the hours are placeholders) The footer of every page; the address and the hours on contact.html
Social links (they open the networks’ home pages), team profiles and award links The footer, About, Contact (Editing the site)
The booking link (https://cal.com/) “Let’s talk” and “Book a Free Consultation”
Titles and descriptions written for your business Each page’s <head>; Home’s title still names the template
Wordmark, icons and share image replaced The wordmark in every page (Making it look like your brand), icon-light.svg, icon-dark.svg, apple-icon.png, opengraph-image.png (2400 × 1260; 1200 × 630 or larger) and its description, og:image:alt
Demo photos, portraits and client logos replaced assets/images/ (Editing the site)
The three stock videos replaced or removed (they play from the Pexels CDN) index.html (Editing the site)
Your services, case studies, posts, team, timeline and awards, or the demo’s removed Home, Services, Portfolio, Blog, About and the pages in service/, portfolio/, blog/ (Editing the site)
Your own figures (“$86M+”, “320+”, “4.9”, “+37%” …) and testimonials, with your clients’ consent Home, About, the case studies (Editing the site)
Your terms and privacy policy (the samples hold [Your Company Name], [URL] and other placeholders) legal/ (Editing the site)
The forms deliver to you, with your wording in the subject assets/js/config.js for the contact form, an action on the newsletter box in every page (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 “Balancee”, the sample e-mail, the sample figures, the testimonials or the legal placeholders on a live site is the most common mistake: search the folder for “Balancee”, “example.com”, “Brooklyn”, “pexels”, “cal.com” and “[Your” one last time.

Everything except the tools and the documentation:

Upload Leave out
The .html pages, service/, portfolio/, blog/, legal/ node_modules/, src/, docs/
assets/ package.json, package-lock.json
icon-light.svg, icon-dark.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, blog/the-power-of-emotional-intelligence-in-leadership.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/firm/, or a GitHub Pages project site), add that folder to those paths.

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 phone menu opening and closing, and the links’ underline on a laptop;
    • the three videos on Home (the hero loops, the About clip plays while on screen, the review plays on click);
    • the clients’ logos running, and the arrows on a phone;
    • the case study rows on Home opening and closing;
    • Portfolio and Blog loading four more as you scroll, a service, a case study, a post, a legal page;
    • the 404 page (open an address that doesn’t exist).
  2. Send yourself a test from the contact form and from the newsletter box, 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 blog current. Add 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 cards the Portfolio and the Blog show later included);
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and share cards (each post with its own photo); 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 font is served from your own domain.

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 hero’s poster, the About photos, a post’s cover) matter most on phones.