Software development companydelivered
A new company website, with existing sub-pages kept in the menu. We did not touch those. Content management is the assistant-based process; publishing is a human hand.
A website that agents fill
The editor shouldn't have to wrestle with HTML
ITLine builds company websites whose content the editor writes and revises with their own AI assistant, with a live preview, from raw material (a document, notes, a talk). The page structure reads cleanly for search engines and AI search alike, and only a person can publish.
The situation
You have something to say, and you have a content manager nobody likes opening. That is why the article never gets written. Not because there is nothing to write about, but because the route to writing it down is longer than the thought.
What we build
A thin frame where the editor works with their own assistant: they hand over the raw material (a document, a note, an earlier talk), that turns into a draft, they look at it live on the page, and they comment on it sentence by sentence until it is good.
The page structure is built so that AI search reads it precisely. That is no longer an extra.
There is one thing this interface cannot do: publish.
Publishing is not the assistant’s job: a human presses it in the editor interface. This is not a permission switched off: there simply is no such operation in its hands.
Cases
Our own sitedelivered
The same frame runs on our own site. What we teach and what we sell, we use ourselves in production.
Common questions
How long does the new website take?
The framework stands up quickly, because the same framework runs our own site; most of the time goes into content. Whether existing subpages stay and how much new material there is gets decided at the survey, and then we give a timeline.
What does such a website cost?
The quote is made after the survey, for a fixed scope. What pushes the price up or down: What it costs.
Do our current subpages and old content stay?
They can. On one delivered site the existing subpages stayed in the menu untouched. We do not, however, migrate a large legacy document platform just to make it newer.
Do we need our own AI subscription?
The editor works with their own assistant, the one they already use. Which one it is, and with what permissions it reaches the content, is fixed at the survey.
What if the AI writes something wrong?
That is why it cannot publish: the editor reviews the draft live on the page, has it revised sentence by sentence, and a person presses the publish button. It is not a disabled permission; the assistant simply has no such action.
What happens to the content and the data?
The content lives on the company’s site and in its storage. What the assistant can see of it, and where it runs, is decided at the survey; the details are settled by contract.
What is not in it
We do not migrate a large, old document platform just so that it becomes the same thing, only newer.
If the goal is replacing the old system, that is a separate conversation, and the answer may well be: do not.