Many independent professionals and small businesses know this chore: updating their own website. Log in, find the right file, remember how the tool works and publish without breaking anything — then, all too often, put it off. The result is an ageing website with last year’s news.
We wanted to simplify that task. The starting point is no longer a tool you need to find again, but a conversation.
What we have put in place
The public pages on karbonic.net are static: HTML files served directly, with no database or plugins needed to display them. Publishing is managed through a separate interface with protected access.
We connected that interface to an AI assistant, using Claude or ChatGPT. In practice, you write: “Add a news item about our 3CX certification” or “Correct the phone number on the contact page.” The assistant reads the relevant pages, prepares the changes and publishes them within the requested scope. The content is reviewed and the result is checked on the website.
This can be done from a computer or a phone. This website update is an example: requests are expressed in everyday language, then applied to the pages and their translations.
This is what we call orchestration: a person decides and clarifies the intention; the assistant coordinates the operations needed to carry it out.
What happens behind the scenes matters
Temporary access, retained versions and checks around each publication.Read moreShow less
Giving an assistant the ability to change a website calls for a clear framework. On this website, publishing uses the following provisions.
- Temporary access. A private link provides access to the interface for a limited period. It allows authorised operations during that time and must be treated as confidential access.
- Retained versions. Each write creates a version. A change can therefore be compared with the previous state and rolled back.
- Traceable changes. Dated versions make it possible to identify the files that changed and their contents. The history helps establish what was modified.
- Defined scope and checks. Pages are read before they are changed. Content, links and layout are checked; published files are compared with the prepared files. AI can make mistakes: these checks are part of the work.
The conversation makes the request easier. Versioning and checks provide a framework for carrying it out.
Why we are sharing this
Because this approach can also be set up for your website. Announce a promotion, change opening hours or replace a photo: once the system is in place, the request can be made in a sentence.
The work involved depends on your website and what you want to change. Access, required approvals and limits are agreed before deployment. Routine changes can then be made without returning each time to a tool you last used six months ago.
The aim is to give you more independence in keeping your website up to date, with support and a defined verification method.