Skip to content
Sign inJoin waitlist

Kendi documentation — HTML

Everything you need to take Kendi for HTML from the downloaded folder to a published blog or magazine. Read in this order, or jump to what you need.

Guide What it covers
Editing the site Opening the site, where everything is, text, images, adding posts, categories and authors, the legal pages, the sponsored ad, adding and removing pages
Pages and sections Every page with a map of its sections, how the pages link to each other, the header, what search engines see
Making it look like your brand How the styling works, rebuilding the stylesheet, colours, the logo and icons, fonts, sizes and spacing, motion
Forms Connecting the contact form and the newsletter to a form service or webhook
Editing without touching HTML Editing without touching HTML: a visual editor, a git-based CMS, or the Astro edition
Going live Pre-launch checklist, what to upload, hosts, your domain, after launch
Troubleshooting and questions Problems, questions and answers
  • 11 kinds of page, 86 addresses:
    • Home (index.html), About, Articles (blog.html), Categories (category.html), Authors (author.html), Contact and the 404 page;
    • a page for each of the 64 posts (blog/), 8 categories (category/), 6 authors (author/) and 2 legal texts (legal/).
  • 2 forms: the contact form and the newsletter sign-up, which appears in three places (Home’s hero, the sidebar card, the band above the footer), posting to any form service or webhook you choose.
  • Articles loads six posts at a time as the reader scrolls; every post is in the HTML, so search engines find them all and visitors without JavaScript see them all.
  • A sponsored ad slot on Home and in the sidebar, with a sample ad to replace with your own.
  • Motion from the original design (the slideshows, labels that roll up, photos that grow, the Categories menu), with reduced-motion support, and a style guide of every component in style-guide.html.
  • Search and sharing: a title, a description and a canonical link for every page, share cards, icons, sitemap.xml and robots.txt.
  • Placeholders: the photos in assets/images/ are grey placeholders that show their sizes (the demo uses photos from Unsplash and Pexels, which can’t be sold with a template). The logo is drawn for the template.
  • These docs (docs/), CHANGELOG.md and LICENSE.md.
  1. Open index.html in your browser, or run npx serve . in the folder and open the address it prints.
  2. Replace https://kendi-html-templategum.vercel.app with your domain in every file, and the demo’s e-mail, phone, address, social links and footer text, with your editor’s find and replace in files (Editing the site).
  3. Replace the images in assets/images/ (keep the file names and you are done): the post covers, the category photos, the authors, the team, the footer’s photo grid and the sample ad (Editing the site).
  4. Replace the logo assets/images/logo.svg, the browser icons (icon.svg, apple-icon.png) and the share image (opengraph-image.png).
  5. Fill in the placeholders of the legal pages ([Your Company Name], [URL] …) in legal/ (Editing the site), and replace the sample ad (Editing the site).
  6. Point the forms at your inbox or newsletter tool in assets/js/config.js: Forms.
  7. Upload the folder: Going live.

Nothing else is required: the site has no database, no build step and no paid service to run.

  • Every page is a file. What you see in the browser is in that page’s HTML: the words, the links, the cards. Blocks that repeat on many pages (the header, the footer, the sidebar, the newsletter band) are copied into each file (Editing the site).
  • Lists are written out. Home’s lists, Articles, the category and author pages and the Spotlights hold copies of the post cards; adding a post means adding its card where it should show (Editing the site).
  • Design is Tailwind classes. The colours, breakpoints and font are tokens in src/css/style.css; the stylesheet assets/css/style.css is built from it and the classes in the pages (Making it look like your brand).
  • One script. assets/js/main.js runs the menus, the slideshows, the loader of Articles and the forms; assets/js/config.js holds your settings.