Edit HTML templates without touching HTML
The HTML edition of every Framebrick template 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; each template’s Editing page shows how.
When someone who doesn’t write HTML needs to publish, you have three honest options.
1. Keep editing the files
Section titled “1. Keep editing the files”For a site that changes a few times a year, this is the right answer. A new post or project is a copied page plus its card in a list or two. 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
Section titled “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.
This is good for text and image changes by a client. Adding a new post 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 an edition built for a CMS
Section titled “3. Move to an edition built for a CMS”If content changes every week — new posts, new roles, new case studies — you want pages generated from a list, where adding an entry creates the page, the cards, the sitemap line and every link at once. That is what each template’s Astro and 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 (Astro templates, Next.js templates). The HTML edition is generated from the Astro edition, so everything you know from its folder carries over.
What not to do
Section titled “What not to do”Loading content 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 marketing site, generate the pages instead (option 3).