The admin isn't the only way to change what a live site says. You can ask the AI to create a post, rewrite the opening of a page, publish or take down an item, fill a field across twenty items or export a form's leads. It uses Velk's content commands, run on the server over SSH (the secure connection the AI uses to work on a server).
This is for content only, what goes inside fields that already exist. A new field, type or page changes the structure: that's made on your computer and published with the theme. A content request never touches the theme.
Ask from the site's project folder, the one you published from or one connected with an access file (see Client sites). If it isn't connected yet, the AI explains how to connect it instead of asking for passwords.
Ask the AI
On the live site of Bright Smile Dental, create a blog post titled “Teeth whitening: what to expect at the first session”, with the text below as the body and a one-sentence SEO description. Leave it as a draft: I'll review it in the admin. [paste the text here]
New items start as drafts unless you ask to publish. The AI reads the post type's fields first, so each part lands in the right field.
Ask the AI
On the live site, replace the opening paragraph of the About page with the text below. Don't touch any other field of that page. “Since 1998, Trigo Bom has baked its bread with natural fermentation, every morning before six.”
Only the fields you name change; the rest of the page stays as it is.
Ask the AI
List the published posts that have no meta description. Write one for each, a single sentence in the tone of the blog, and show me all of them before saving anything.
Batch edits are where a conversation beats the admin. The SEO fields are built into every page and every item with a page of its own.
What the AI does
-
Reads the site first
It lists the site's content types and pages and reads the fields of the one it will touch (
item:schema,page:schema). It never assumes there is a blog or guesses a field name. -
Tests without saving
Each creation or change runs first with
--dry-run, which checks required fields, types and addresses without writing anything. -
Asks for your yes
It shows exactly what will change: which fields, which items, how many. To delete several items it lists their addresses and waits for an explicit confirmation.
-
Backs up the content
Before writing, it saves the content tables (
itemsandpages) to a private file on your computer and tells you where. -
Writes and reports
It runs the real command and tells you what changed and where the backup is.
What you can ask for
| Request | How it's done |
|---|---|
| Create a post, a case, a service: any content type | item:create. A draft unless you ask to publish; the address comes from the title. |
| Change a title, a text, the address or any field | item:update. Only the fields you name change. |
| Publish or take down | item:publish, item:unpublish (back to draft). |
| Change the home, the About page or another page of the structure | page:update, which also changes only what you name. |
| SEO title, description, share image | Built-in fields. An image must be in the media library first. |
| Delete | item:delete, after you confirm. There is no trash. |
| A theme block inside a text (since v3.9.0) | It goes into the text field; the commands refuse a block written wrong and name the field. |
| Export a form's leads (since v3.8.0) | form:export: a spreadsheet file (CSV) of the approved, completed submissions. |
Ask the AI
Export the September leads of the agency's quote form to CSV, with the campaign columns (UTM). Save the file as leads/quote-september.csv and don't paste its contents here.
It's the same file as the Export block on the form's screen in the admin: spam, and multi-step leads still in progress, stay out.
When the admin is better
Some things the content commands don't do. In the admin they take a click:
- Uploading images and files. Put the image in the media library first; the AI can then use it in a field.
- Categories and tags, attached in the item's editor.
- Translations. The commands write the default language; the other languages' tabs are filled in the admin.
- Options and the menu (logo, phone, social links, footer) and pages created in the admin from a page template.
- Drag-to-order lists, and one-off edits you want to watch as you type.
A conversation wins on volume and repetition: twenty items at once, the same fix across a section, a batch of drafts to publish.
Questions
Does the AI need the admin or database password?
No. It works over SSH with the connection saved in the project, and the commands read the database settings on the server. A computer connected with an access file never receives the database password.
What if the AI says a command doesn't exist?
The site runs a Velk too old to have the content commands. Update Velk on the server first (see Update Velk).
What if the connection drops in the middle of a change?
The AI doesn't resend on its own, since a repeat could create the same post twice. Ask it to list what's there before trying again.