Troubleshooting — Denzel HTML
Most problems in Denzel’s HTML edition come from a wrong number of ../ in a path, a class the stylesheet lacks, an
unchanged copy, a broken search list or an empty form endpoint.
The answers below cover those first (a copy is a block written into several pages, one of them left unchanged), then the questions buyers ask most.
Problems you may hit
Section titled “Problems you may hit”The page looks unstyled.
The browser can’t find assets/css/style.css. Pages inside a folder (blog/…, category/…, author/…) link to it as
../assets/css/style.css; a page you moved or created may have the wrong number of ../. 404.html looks unstyled
when you open it from disk, and that’s expected: its paths start at the site’s root, which works on a host or with
npx serve . (Going live).
An image doesn’t appear.
Check the path in src against the file in assets/images/: spelling, extension, and ../ in pages inside a folder.
File names are case-sensitive on most hosts even when they are not on your computer: Post-Cover.JPG is not
post-cover.jpg.
A photo is cropped in the wrong place. Every photo fills a fixed frame and loses the edges the frame cuts, and the same cover shows in wide, tall and round frames. Choose a photo with the subject near the middle, or crop it to the frame’s shape first (Editing the site).
A class I added does nothing.
assets/css/style.css only contains the classes the site already used. Rebuild it with npm run build:css
(Making it look like your brand).
I changed something, but another page still shows the old version. The pages hold copies, not references: the header, the footer, the sidebar, the search list and every card of a post are written into each page that shows them (Editing the site). Search the folder for the old text.
The search doesn’t open, or finds nothing. The search list in that page is not valid JSON any more (a missing comma or quote, a comma after the last entry): open the developer tools → Console for the error, and compare it with the list in an untouched page (Editing the site).
The search doesn’t find my new post. It only knows what is in its list, and the list is written into every page: add the post’s entry to all of them.
A search result opens a page that doesn’t exist.
Its href must be the page’s file from the site’s root, with .html (/blog/finding-your-calm.html). Opened from disk
(file://…), the results can’t work, because they start at the root: try them on a host or with npx serve ..
The menu, the search or the slider stopped working.
assets/js/main.js or assets/js/config.js is missing, or an element lost a data-… attribute or an id when you
edited it. Open the browser’s developer tools → Console for the error, and compare the markup with the same element
on an untouched page.
The menu highlights the wrong page.
The current page’s link carries aria-current="page" and the grey struck-through look (text-grey line-through); in a
copied page, that mark is the original’s. Move it in both menus (Editing the site).
The slider doesn’t move.
It moves only when there are more posts than fit on the screen (four on desktops), and stands still when the visitor has
“reduce motion” switched on. If it jumps or shows a gap, check data-count against the number of slides and the four
copies after them (Editing the site).
Nothing glides: the menu, the search, the slider. The visitor’s system (yours, if you see it) has “reduce motion” switched on, and the site honours it (Making it look like your brand).
The counts in Explore Topics are wrong. They are text (“8 Post”): change them in every page with a sidebar when you add or remove a post.
The newsletter says “Something went wrong”.
The form service rejected the sign-up or couldn’t be reached. Check formEndpoint in assets/js/config.js, then open
the developer tools → Network, sign up again and read the service’s response. Web3Forms also needs formAccessKey.
Some services require you to confirm your email address before the first submission goes through.
The newsletter says “Thank you!” but nothing arrives.
formEndpoint is empty, so the box is still in demo mode (the e-mail is logged in the browser console).
Clicking a link downloads a file or shows a directory listing.
The link points at a folder or lacks .html. Links in this template always end in .html.
The share image or title is the old one.
Facebook, LinkedIn and X cache them. Use their debuggers to refresh, and check that the og:image URL uses your domain.
Questions
Section titled “Questions”Do I need Node.js or a build step? No, only to rebuild the stylesheet after changing the theme or using new classes. Everything else is editing HTML.
Can I use this template for a client? See License: that is the one place that answers it for your licence.
Can I remove the style guide, a page, a section or a category? Yes:
- the style guide: delete
style-guide.html; - a page: Editing the site;
- a block: delete its markup, for example the slider’s
<section>, Trending, or a box of the sidebar; - a category or an author: delete its page, its menu link, its cards’ links, its Explore Topics entry, its search entry and its sitemap line; move its posts to another one first.
Can I change the fonts to my brand’s? Yes: Making it look like your brand.
Can I write the site in another language?
Yes: write the text in your language and set lang="en" on each page’s <html> and og:locale (en_US) in its
<head>. The dates are written as text, so write them your way (keep the datetime as 2023-09-14). The font files
hold Latin letters only (English and most Western European languages); for other alphabets, add the matching files of
Noto Serif JP and Poppins (design.md, Fonts). The template has no language switch.
Does the site need JavaScript?
For what moves and for the interactive parts: assets/js/main.js runs the phone menu, the search, the slider, the
newsletter box and the footer’s year. Without it, every text and every card still shows, but the phone menu and the
search don’t open, the slider stands still and the newsletter can’t send. Every word and link is in the HTML, so search
engines read the whole site.
Does the site need a cookie banner? As shipped, the template sets no cookies and loads no third-party scripts: the fonts are served from your own domain. Any analytics you add is yours to declare.
Can I use it with WordPress, Webflow or a site builder?
Not directly: it is plain HTML and CSS. You can paste sections into a builder that accepts custom HTML, but the
interactions rely on assets/js/main.js.
Can I connect a CMS? See Editing without touching HTML for the options, including the Astro and Next.js editions built for one.
How do I update to a new version of the template?
CHANGELOG.md in the new release lists what changed. For a script or style fix, replacing assets/js/main.js and
assets/css/style.css is usually enough (run npm run build:css again if you added classes of your own or changed the
theme). Page changes are listed so you can apply them to your edited pages.
Can you customise it for me, or build my site? Yes. Marcframe, the studio behind this template, updates templates to your needs (brand, content, new pages and features), builds custom templates and designs new websites. Get in touch at marcframe.com/contact or hire us on Contra.
Something is broken and none of this helps. Support and updates: https://framebrick.co/support. Send the page, the browser, and the error text or a screenshot: it makes the answer much faster.