Denzel documentation — HTML
Everything you need to go from the downloaded HTML folder to a published blog or magazine, in the order to read it.
| Guide | What it covers |
|---|---|
| Editing the site | Opening the site, editing text, links and images, the blocks that repeat, the search list, adding and removing posts, categories, authors and pages |
| Pages and sections | Every kind of page, its sections, where its text and photos are, and how the pages link to each other |
| Making it look like your brand | Colours, the logo and icon, the two fonts, the Tailwind classes, rebuilding the stylesheet, the style guide and motion |
| Forms | Making the newsletter box deliver to you |
| Editing without touching HTML | Your options when someone else needs to edit the site without touching HTML |
| Going live | Pre-launch checklist, uploading, domains, what to do after launch |
| Troubleshooting and questions | Errors, questions and answers |
In a hurry: the first 15 minutes
Section titled “In a hurry: the first 15 minutes”- Open
index.htmlin your browser. That is the whole site: no install, no build. - Open the folder in a code editor (VS Code is a good free one).
- Replace the e-mail, the social links and the demo domain across all files with your editor’s find and replace in files (Editing the site), then search for “Denzel” to put your own name in the titles and the footer.
- Replace the photos in
assets/images/: keep the file names and every page picks them up (Editing the site). - Replace the logo (Making it look like your brand), the icons and the share image in the root folder
(
icon.svg,apple-icon.png,opengraph-image.png). - Put your form endpoint in
assets/js/config.js(Forms). - Upload the folder to your host (Going live).
How this template is put together
Section titled “How this template is put together”- One HTML file per page.
blog.htmlis/blog.html; each post, category and author has its own file inblog/,category/andauthor/(Pages and sections). - One stylesheet.
assets/css/style.css, built fromsrc/css/style.csswith Tailwind CSS. You only rebuild it when you use a class that isn’t in the site yet, or change the theme (Making it look like your brand). - One script.
assets/js/main.jsruns the phone menu, the search dialog, the featured slider on Home, the newsletter box and the footer’s year. You rarely need to touch it: your settings go inassets/js/config.js. - Copies, not references. A block that shows on several pages (a post’s card, the sidebar, the footer, the search list) is written into each of them. Change every copy, or use find and replace in files (Editing the site).
- No framework, no dependencies at runtime. The pages work from any static host, and even straight from disk.
A blog grows by a post at a time, and in this edition each post is a dozen edits by hand. If you will publish every week, choose the Denzel Astro or Denzel Next.js edition instead: a new post is one entry in a data file, and every list, count, search entry and sitemap line follows (Editing without touching HTML).
Getting help
Section titled “Getting help”- Your licence terms: License.
- What changed in each release: Changelog.
- Support and updates: https://framebrick.co/support.
- Want it done for you? Marcframe, the studio behind this template, updates templates to your needs, builds custom templates and designs new sites. It’s also on Contra.