Every content platform has AI in it now. Almost all of it is the same thing: a page editor with a button in the corner that will help you write a paragraph, if you ask it, while you are already in the editor doing the work.
That is a content management system with a feature stapled to it. It does not change who does the job. You still open the tool, still face the empty page, still assemble the site by hand. The button helps with the typing, and typing was never the hard part.
The software does the work. Your staff say yes or no.
That sentence is the whole design, and it points the other way.
Nobody starts from a blank page
Work in Baseline starts with information your town already maintains. A department page. A public notice. A document from a board.
Staff choose the existing pages, news, or converted documents the AI can use, then ask for a new draft or a rewrite. The software can also prepare a draft page from a document containing text. Your staff check the details, edit the content, and decide whether it is ready to publish. Scans and photographs of pages cannot be converted yet.
If a screen in our product asks a Town Clerk to write something from nothing, we got that screen wrong and we would like to hear about it.
It starts before you are a customer
The first thing we look at is the website you already have: your departments, your boards, your content. We assess what can move into Baseline and what needs a person's attention. Some hosts block automated migration, and some pages need hands-on work.
Two reasons that matters. You should be able to judge a platform by looking at your own town rather than somebody else's demo. And the hard part of switching, the thing that keeps towns on software they dislike for the better part of a decade, becomes our problem instead of yours.
The jobs nobody gets to
Rewriting a service page for clarity. Preparing a summary. Turning information in a document into a readable page.
These are what gets dropped at four in the afternoon on a busy day, and they are also what gets a town in trouble. They are exactly what a machine is good at. It is the least exciting argument for AI in government software and probably the strongest one.
Now the catch
Software that writes most of your website had better not be able to write a broken one. Otherwise you have automated the problem and made it faster.
So nothing here writes the underlying code. Not your staff and not the AI. Both work with pieces we built and checked first. The software cannot invent a heading structure, cannot pick a color, cannot hand-roll a widget. It has a vocabulary, and everything in that vocabulary was tested before it ever got used.
That is a real constraint and we are not apologising for it. It is the thing that makes the rest safe to ship.
And a person still says yes
Nothing the software produces goes public on its own.
You see what changed before you approve it. Your town defines the sequence of people who need to sign off. The record of revisions and approvals stays with the content, because a town publishing this kind of information should be able to explain its decisions.
A town gets held to account in ways a business does not. Software that quietly reworded a page of bylaws is not a bug you file on Monday. It is a phone call from your attorney. So approval is something we advertise rather than something we apologise for.