Skip to content
Sign inJoin waitlist

Going live — Kendi HTML

Publishing the Kendi HTML edition means replacing the demo’s magazine and pictures, filling in the legal pages, 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.

Where
Demo domain replaced by yours Every .html file, sitemap.xml, robots.txt: find https://kendi-html-templategum.vercel.app (Editing the site)
Your magazine’s name instead of “Kendi”: the copyright, About, Contact, the page titles and share tags Search the folder for “Kendi”
Contact details: the e-mail, phone, address and hours are made up contact.html
Social links (they open the networks’ home pages), the authors’ links and the footer grid’s links The sidebar, the footer and Contact of every page, the author pages
The sidebar’s About text (“We influence 20 million users…” is the demo’s claim) Home and every post
The legal pages: every placeholder filled in ([Your Company Name], [URL], [Contact Information], [Your Jurisdiction], [Arbitration Location], [Link to Privacy Policy]) and the texts checked for your site legal/ (Editing the site)
The sponsored ad replaced with your own, or removed (Tenq Tech is a made-up advertiser) Home and every sidebar (Editing the site)
Your posts, categories, authors and team The pages in blog/, category/, author/, and every list that shows them (Editing the site)
Titles and descriptions written for your site Each page’s <head>; Home’s still describe the template
Logo, icons and share image replaced assets/images/logo.svg (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 replaced assets/images/
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 “Kendi”, the sample e-mail and phone, the demo posts and authors, the sample ad or the legal placeholders on a live site is the most common mistake. Search the folder for “Kendi”, “Tenq” and [Your one last time (the forms’ placeholder hello@example.com can stay).

Everything except the tools and the documentation:

Upload Leave out
The .html pages, blog/, category/, author/, 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.

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/<slug>.html), so no server configuration is needed. Three demo posts have a typographic ’ in their file name, linked encoded (%E2%80%99); common hosts map one to the other, but check one of them after uploading. 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/magazine/, 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 menu, the Categories menu on desktop, the tablet and phone menus;
    • the hero slideshow and the Inspiration carousel;
    • Articles showing more posts as you scroll;
    • a post with its sidebar and Related Post, a category page, an author page;
    • the ad’s button, the footer’s links and legal pages, and the 404 page (open an address that doesn’t exist).
  2. Sign up and write to yourself — the newsletter from Home, the sidebar and the band, and a contact message — and reply to the message.
  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 publishing. 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 — every post of Articles too, even the ones that appear on scroll;
  • one <h1> per page, and a title and description for every page;
  • canonical links, sitemap.xml, robots.txt and 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.

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 slides, the post covers) matter most on phones.