Why cmsspot
A plain site, and an owner who can edit it
Most business websites are a handful of pages that change a few times a year. The best way to build those is plain HTML or PHP. The only thing that was ever missing was a way for the owner to change a sentence without calling a developer. That is the whole of what cmsspot does, and this page is the case for it.
Who it is for
Agencies and freelance developers who build sites by hand and hand them to clients. Clients who want to fix a price, swap a photo or add a page, and never see the code. And, increasingly, the AI assistant that one of them asks to do the work.
cmsspot is a file-based headless CMS: the editor is separate from the site, and the content is your own files. What that means, and what it does not.
Three reasons
1. The site stays plain
cmsspot is never installed on the site. It connects over SFTP, reads the pages as data, and writes back only the field that changed. A visitor gets the page you wrote, byte for byte, with the new text in it. No database, no plugins, no update schedule, nothing that runs on a visit, nothing that slows down over time. That is why it is fast and why there is so little to attack.
2. Nothing to tag, nothing to rebuild
Open a page in cmsspot and it is already fields: headings, paragraphs, images with alt text, links, buttons, the menu. It understands PHP sites with includes, gives the header, footer and menu their own tabs, and edits a title set as a variable the way the site expects. Shared values become globals, repeated blocks become groups. How it works.
3. The owner gets exactly enough
Text, images, links, menu, titles and descriptions, new pages. Not the layout, not the code, not the server. The owner cannot break the design by accident, and the developer never has to hand over a password. The SEO box shows lengths in colour and checks schema as it is typed, so the owner gets it right without being told. See it.
And one more
An AI assistant can be given a token for one site at one of three levels, with files you hide and a log of every call. "Go through every page and shorten the titles over 60 characters" becomes an afternoon's work done in a minute, and you review it before the client sees it. AI & SEO.
What you give up
Be clear about this before you choose. cmsspot has no shop, no user accounts, no comments, no approval workflow, no scheduled publishing, and no multilingual content model. It does not host the site and it does not build it from a generator. Articles are pages in a folder, not a blog engine with categories and archives.
For the sites cmsspot is made for, none of that is missing. For a site that needs it, use the tool built for it. The comparisons say which.
When to choose something else
- A shop with carts and payments, or members: WordPress with WooCommerce, or a dedicated shop platform.
- Hundreds of posts from several authors with drafts and roles: WordPress or Drupal.
- Structured content used in many places, several languages or a team of editors: Sanity or another headless CMS.
- A static site generator and a Git workflow: CloudCannon or Decap, in the alternatives.
- A full file-based CMS installed on the site with content modelling: Kirby, same page.
- Nobody who can write HTML, and the site has to exist tomorrow: Squarespace or Wix.
How to find out in ten minutes
Create an account, connect a site you already have, and open one page. If the fields are there and the save touches only what you changed, you have your answer. If the site is a builder export with no real headings, you have a different answer, and the build guide can help you convert it.
Get started
Try cmsspot on your own site
Connect a site, edit a page, see how little it touches. Free to start.