Troubleshooting — Findit HTML

Problems you may hit

The page looks unstyled. The browser can’t find assets/css/style.css. Pages inside a folder (property/…) link to it as ../assets/css/style.css (and ../../assets/css/style.css in filter/…); a page you moved or created may have the wrong number of ../.

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: Team.JPG is not team.jpg.

A class I added does nothing. assets/css/style.css only contains the classes the site already used. Rebuild it: npm run build:css (Making it look like your brand).

Menus, sliders, filters or accordions stopped working. assets/js/main.js or assets/js/config.js is missing, or an element lost a data-… attribute 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 form says “Something went wrong”. The form service rejected the submission or couldn’t be reached. Check formEndpoint in assets/js/config.js, then open the developer tools → Network, submit 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 form shows “Thank you” but nothing arrives. formEndpoint is empty, so the form is still in demo mode (the fields are 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.

A new property doesn’t show in a list or in search. It has a page but no card in that list, or no line in sitemap.xml (Editing the site).

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.

The video on the home page does not play. The demo plays a clip from Pexels’ servers and is not part of the download. Replace the src of the <video> in index.html with your own file or a link to one (Editing the site).

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 / the home page video? Yes. Style guide: delete style-guide.html. A page: Editing the site. The video: Editing the site.

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); 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.