Skip to content
Sign inJoin waitlist

Going live — Denzel HTML

Publishing Denzel’s HTML edition means replacing the demo’s details, pictures and sample posts, pointing the newsletter 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://denzel-html-marcframe.vercel.app (Editing the site)
Your name instead of “Denzel”: the logo, the titles, the breadcrumbs, the footer note (“Theme by Marcframe” too, if you like) Search the folder for “Denzel”
Your e-mail (hello@example.com is a placeholder) The footer of every page
Social links (they open the networks’ home pages), and each writer’s own The header, the phone menu, the sidebar, the footer; the author pages
Titles and descriptions written for your site Each page’s <head>; Home’s title and description still name 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/ (Editing the site)
Your posts, categories and writers, or the demo’s removed; the default Uncategory and Admin kept or deleted blog/, category/, author/ and every list that shows them (Editing the site)
The counts of Explore Topics and “Join 89,000 subscribers!” true for your site Every page with a sidebar; the footer
The search list matches your pages Every page (Editing the site)
The newsletter delivers to you, with your wording in the subject; a privacy page linked under it 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 “Denzel”, the sample e-mail, the sample posts or the demo’s counts on a live site is the most common mistake: search the folder for “Denzel”, “example.com”, “89,000” and the title of a demo post one last time.

Everything except the tools and the documentation:

Upload Leave out
The .html pages, blog/, category/, author/ 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 (blog.html, blog/self-driving-cars-everything-you-need-to-know.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. Two things start at the site’s root: the paths in 404.html (/assets/css/style.css, /index.html), because hosts show it at any address, and the addresses in the search list (/blog/<slug>.html). 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 phone menu opening and closing;
    • the slider on Home moving every five seconds;
    • the search: type a word, open a result with the mouse and with Enter;
    • the Blog page, a category, an author, a post with its Related Posts and More Articles;
    • the 404 page (open an address that doesn’t exist).
  2. Sign up to the newsletter yourself and check that it arrived.
  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 and the search list in step.

The pages ship with what search engines look for:

  • real HTML, with links in it to every post, category and author;
  • 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 cover); 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 fonts are served from your own domain, in their Latin letters only (seven small files).

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 slider’s, a post’s cover) matter most on phones.