LessHeadCMS Reviews and Details

Questions & Answers

1. What makes LessHeadCMS unique?

   LessHeadCMS turns a PlantUML class diagram into a complete headless CMS: database tables, a paginated REST API and an editorial interface are all generated from one text file. Instead of clicking content types together in settings screens, you model them – and the same diagram can be discussed with clients, versioned in Git and changed later through a reviewed schema diff with automatic backup.

   It runs on ordinary shared hosting with PHP and SQLite, and even editorial approval workflows are defined as short text blocks.

2. Why should a person choose LessHeadCMS over its competitors?

   Choose it if you want a real headless CMS without the infrastructure that usually comes with one: no Node.js, no Docker, no cloud subscription and no limits on users, roles, languages or records.

   Features that other systems reserve for paid plans – field-level permissions, approval workflows, schema migrations with backups – are included and free under the AGPL v3. It is not trying to replace large enterprise platforms; it is built for projects where a clear content model, low hosting requirements and full control over your own data matter more than a huge plugin ecosystem.

3. How would you describe the primary audience of LessHeadCMS?

   As of now: Freelancers, small agencies and developers who build websites and apps for clients and want to give them a lean, tailor-made backend – often on the PHP hosting the client already has. A second audience is the editors on the client side: they get forms that match their content exactly, so they can work without training.

   It also suits anyone who wants to develop a content structure together with a client in a workshop, because the diagram doubles as the specification.

4. What's the story behind LessHeadCMS?

   I have been building websites since the mid-1990s and ran my own agency for ten years. With established headless CMSs, I kept finding that setting up the data structure was the most tedious part – endless configuration screens for something that is, at its core, just a diagram. So I asked: why not start with the diagram itself? LessHeadCMS began as an experiment to generate a usable CMS directly from a UML model and grew into a full system with permissions, workflows, migrations and translations – deliberately kept small enough to run on the kind of hosting most small businesses already pay for.

5. Which are the primary technologies used for building LessHeadCMS?

   The backend is written in PHP 8 with the FlightPHP micro-framework and stores all data in SQLite via PDO. Content models are written in PlantUML and parsed into the database schema. The editorial interface is built with Preact and Vite and ships as prebuilt static files, with Toast UI Editor for rich text stored as Markdown. Quality is secured with Playwright browser tests, runtime migration tests and a schema fuzzer that checks thousands of randomly generated models.