AI site management · client work
The site its owner edits by chat
The owner of Siamese Edge runs a sword forge, not a website. He logs in, sees his own site with a number on everything he can change, and types what he wants in Thai or English. The change appears as a draft. When he is happy, he presses Publish.
- client
- Siamese Edge · Thailand
- role
- product · design · build
- status
- live on the forge’s own site · November 2026
01why it exists
He should not need me to change a price.
The forge’s site was rebuilt as fast, plain pages with nothing to patch and nothing to hack. That is good for visitors and bad for an owner: there is no admin screen any more, so every new sword, photograph or price would have meant a message to me.
The editor gives him his site back without giving him a content system to learn. He browses his own pages as he always has. The only new things are a chat on the left and a small number on everything he is allowed to change.
He is not technical and he thinks in Thai. Both facts shaped almost every decision below.
- 30
- kinds of edit the assistant can make, each one checked
- 0
- lines of HTML written by the model
- 99.3%
- right on 300 test requests, most in everyday Thai
- 0
- edits to locked things, and no guesses where a question was due
- 1.4 s
- typical reply
- 1
- button to publish, and one to take it back
02watch him edit
Real sessions, step by step.
Choose a request, then step through what was typed, what the assistant answered and what changed. Recorded on a private copy of the site; the replies are the assistant’s own.
Two sentences on the home page are reworded by describing them in plain English.
The home page banner before.
03what he can do
Features.
By chat
- Change any text; reword it, or dictate it exactly
- Replace pictures and backgrounds from his own uploads
- Add to a gallery, reorder it, take pictures out
- Move, copy or remove sections and columns; add text, pictures, galleries, videos and buttons
- Add a product: one message makes its card in the list and its own page
- Create a page and put it in the menu; rename menu items; change contact links
By hand
- Point at anything for its controls: edit, move, add, copy, remove
- A rich text editor for headings, bold, colour and lists
- New pages arrive with grey boxes; click one to fill it
- A picture picker with his uploads and every picture already on the site
- None of this calls the AI
Drafts and publishing
- Every edit goes into one draft, across as many pages as he likes
- The draft survives logging out; visitors see nothing until he publishes
- Each change can be undone on its own
- Publish shows the list of changes first, in plain words
- Restore previous version puts back what was live before
His language
- The editor opens in Thai, with English one tap away
- Requests in Thai or English; the reply comes in the language he used
- Short codes for speed: “swap c1 c2”, “remove gi3”
- Thai file names are kept; Thai numerals are understood
Pictures and video
- Uploads are resized in his browser to three sizes before they travel
- Videos are links to where they already live, shown as click-to-play
- After publishing, it offers to delete uploads nothing uses
- “On the site” shows where every picture is used
On a phone
- The tray slides over the page from a round button
- Labels stay on, with their controls
- The same chat, the same draft
04the screens
Up close.
05decisions
Why it is the way it is.
- safetyThe model never writes the page.
- It cannot produce HTML at all. It chooses from thirty edit operations, and every choice is checked against the page’s real list of things before anything changes. In one recorded session it miscounted a gallery; the check refused the edit, nothing changed, and the tray said so. A wrong answer costs him a retry, never a broken page.
- the customerA number on everything he can change.
- “The second picture” means something different to each of us. Every text, picture, button, section and menu item carries a short label, so he can say it in his own words or just type the code. What cannot be edited shows a padlock instead of nothing.
- the customerIt asks instead of guessing.
- If a request could mean more than one thing, he gets one question with the answers as buttons to tap. On a page with several galleries the server forces that question, whatever the model thinks. A wrong guess on a live shop is worse than one extra tap.
- safetyBig removals wait for a yes.
- Removing a section, a page, a menu item or more than three things at once names what will go and waits. The site’s original pages cannot be deleted at all.
- honestyLocked things get a fixed answer.
- The 3D viewer, the configurator, the map and the fields of the order form are not his to break. Asking to change them returns one sentence written in advance, not something the model made up, and the draft is untouched.
- his voiceHis words are his words.
- Text he dictates is never “improved”. The prompt carries a glossary of the words he actually uses for his swords and his site, and the test set is a hundred requests, mostly vague or colloquial Thai, each run three times.
- peace of mindNothing is public until Publish, and Publish can be taken back.
- The draft and the live site are separate, and publishing is one switch from one to the other, with the previous version kept. A “Save draft” button stayed in the tray even though saving is automatic, because he expected one and looked for it.
- restraintNot everything should need the AI.
- After watching him use it, the hover controls, the text editor and the grey placeholder boxes were added. Fixing a typo should be a click. The grey boxes also mean a new page cannot be published half-finished without him seeing that it is.
- layoutThe tray never covers what he is changing.
- It sits to the left of the page, not over it, so he watches the change happen. On a phone, where there is no room, it slides away after each edit.
- resilienceIf the assistant is unavailable, the page is left alone.
- A failed or slow reply changes nothing, and the hand tools still work. Edits are stored as a list of operations rather than as changed files, so they survive the site being rebuilt underneath them.
06not done yet
What these recordings turned up.
- Reordering a gallery by a loose description (“move the last one to the front”) can miscount; the check stops it, and naming the picture works. It should just work.
- On a phone, pages with wide galleries push the tray’s button off the screen.
- A new page borrows its neighbours’ layout, and sometimes a line of their text; it should arrive empty.
[client work · the site and its pictures are the forge’s own · the same forge’s swords: the sword configurator →]