Editing without touching HTML

The HTML version is deliberately simple: the content is written into the pages. That is what makes it fast, free to host and easy to hand over — and it also means there is no admin panel. You edit files (Editing the site).

A property site changes more often than most. When someone who doesn’t write HTML needs to publish, you have three honest options.

1. Keep editing the files

For a site with a fixed set of listings, or one that changes a few times a year, this is the right answer. A new property is a copied page plus a card in a handful of lists (Editing the site). With the folder in a Git repository connected to Netlify, Vercel or Cloudflare Pages, you can even edit a file in GitHub’s web editor and the site redeploys by itself.

2. A visual editor on top of the HTML

Some services edit static HTML in the browser, with the page as it looks, and publish it for you. CloudCannon is the best known: connect the Git repository, mark the regions editors may change with its data-editable attributes, and they edit text and images visually.

Good for text and image changes by a client, such as a price or a description. Adding a new property still means copying a page and its cards, since the site has no templates. (Git-based CMSs such as Decap or Pages CMS edit Markdown and JSON files, not finished HTML pages — they fit the Astro edition, not this one.)

3. Move to a version built for a CMS

If listings change weekly — new properties, sold ones taken off, new agents and posts — you want pages generated from a list, where adding an entry creates the page, the card in every list, the filters, the sitemap line and every link at once. That is what the Findit Astro and Findit Next.js editions are: the same design, pixel for pixel, with content in data files and a documented path to Sanity, Payload, Strapi, Directus or any headless CMS. The HTML version is generated from the Astro edition, so everything you know from this folder carries over.

What not to do

Loading listings from a headless CMS with JavaScript in the browser works technically, but search engines and share cards then see empty pages, and every visit waits for the API. For a property site, where every listing should be found in search, generate the pages instead (option 3).