Going live — Semono HTML
Publishing the Semono HTML edition means replacing the demo’s details, pictures and videos, pointing the forms 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://semono-html-templategum.vercel.app (Editing the site) |
| Your firm’s name instead of “Semono”: the copy, the footer, the testimonials’ quotes, the posts, the careers and the legal texts | Search the folder for “Semono” |
Contact details (hello@example.com, the phone number and the address are placeholders) |
The footer of every page and the Contact page |
| Business hours | contact.html |
Your booking link (“Book a free consultation” on Home opens https://cal.com/) |
index.html |
| Social links and the team’s LinkedIn links (they open the networks’ home pages) | The footer of every page; the team cards on About and Team |
| The line about the firm and the taglines in the footer | Every page |
| Titles and descriptions written for your work | Each page’s <head>; Home’s still describe the template |
| 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 |
| Demo photos, portraits and client logos replaced | assets/images/ |
| The two videos and their posters replaced (or removed) | Editing the site |
| Your own figures: projects, partners, satisfaction, reach; the figures of each service | Home, About, service/ |
| Testimonials from your own clients, with their logos and results | Testimonial, Home, Services, About (Editing the site) |
| Your services, team, posts and open positions | The pages and their lists (Editing the site) |
| Legal texts of your own (the demo’s Privacy Policy and Terms of Service are samples) | legal/ |
| The Contact form’s service choices match your services | contact.html (Forms) |
| The forms deliver to you | assets/js/config.js (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 “Semono”, the sample e-mail, the sample figures, the testimonials, the legal texts, the stock videos or the
sample client logos on a live site is the most common mistake: search the folder for “Semono”, “example.com” and
“pexels” one last time (the forms’ placeholder jane@example.com can stay).
What to upload
Section titled “What to upload”Everything except the tools and the documentation:
| Upload | Leave out |
|---|---|
The .html pages, service/, career/, blog/, legal/ |
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, service/business-strategy.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.
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 header over the Home photo turning light at “About Semono”, and the phone menu;
- the page change when you follow a link;
- the accordion, the process tabs (rows on a phone) and the testimonial cards on Home;
- the logo ticker, and both video cards (press play);
- Services, Testimonial and the Blog loading more as you scroll;
- a service page, a post, a career page and the FAQ on Contact;
- the 404 page (open an address that doesn’t exist).
- Send yourself a test from each form (an inquiry, a consultation request, an application) and reply to it.
- Verify the share card. Paste the URL of the home page and of a service or 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 services, posts and positions 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 later items of Services, Testimonial and the Blog 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 videos load only when pressed.
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, the wide photos of About, the services and the posts) matter most on phones.