Web development
Web Base: the new stage of the project
The Astro base web is no longer a template: it's a multi-client AI-native CMS
2 min read
Two weeks ago I explained here how I was building a reusable base web: an Astro template with its own panel, so as not to start every client website from scratch. This project has grown faster than I expected and today it deserves a formal presentation: it's called Web Base and it's no longer a template, it's a product.
What Web Base is now
The idea remains the same as always: not repeating work between clients. But the scale changed. Today Web Base is a multi-client AI-native CMS/blog:
- A common core (API + admin panel + signed updates system) identical for all clients.
- A public website per client, generated in minutes from an Astro template, with its own repository and image.
Or in plain words: I install the same base for each client, and each one has its own website, its panel and its updates — but I maintain a single core, not ten different projects.
What the core brings
All this already works, it's not a wish list:
- Content: articles with rich editor and auto-saving, editorial calendar, multilingual, WordPress-style media library (folders, WebP/AVIF, drag and drop).
- Integrated AI: article generation from an idea or by analyzing competitor websites, generated images with alt texts, assisted SEO, and even autonomous publications: the system plans, writes, illustrates, translates and publishes on its own, with anti-duplicate included.
- Operations: moderated comments, cookie-less own analytics, backups, wiki and a public development journal on each installation.
The part I like the most: signed updates
The system I'm most proud of is the updates circuit. I publish a new version of the core, it's built automatically, cryptographically signed and each client receives it with a confirmation button from their own panel. If the package isn't exactly what I signed, it doesn't install. It's the mechanism used by serious Linux distributions, applied to a custom CMS.
The repository family
The project now lives in several repositories, each with its own role:
wb-core: the core (API, panel, updater, installers)wb-frontend-template: the Astro template of public websiteswb-web-base: the website of the product itselfwb-becoach-biz: the first real client websitewb-dev-journal: the development journal and living documentation
And now what?
Two things. First: this journal continues here, day by day, with what breaks, what gets fixed and what gets decided — now under the name Web Base. Second: in the coming days I have a small backlog of pending entries to publish; I'll post them all at once and then the rhythm returns to daily.
If you want to read the story from the beginning: the day I started this base web wasn't about this — the construction of the Astro base began at the introductory post.