A Velk site has three parts: the structure is a file (site.json), the content is in the database, and the look is the theme — the page templates in theme/templates/, the shared pieces such as the header and the footer in theme/partials/, and the CSS (the style rules), scripts and images beside them. Everything a visitor sees — colors, fonts, spacing, layout — comes from the theme, and the AI writes it.
The client changes content in the admin, never the look. A new post or a new block always comes out in the site's design, and the panel has no way to change the layout.
Asking for a visual change
- Give a reference. A site you like, the brand manual, color codes and font names, a mockup (an image or a PDF attached to the conversation). “Modern and clean” means nothing to anyone; “cards like the ones on this page, in our blue
#1A3D8F” does. - One change at a time. “A bigger title in the hero”, then “more space between the services”: two requests you check one by one.
- Say where it applies — only the home, every page, only the posts — and what must not change.
- Check on a phone. Narrow the browser window or open the page on a phone, and describe what breaks: “on the phone the menu covers the logo”.
Ask the AI
On the home page hero (the large opening section), make the title bigger — about 56px on a computer, 36px on a phone —, keep the font, and leave more space between the title and the button. Don't change anything else on the site.
A change you can measure, in one place, saying what stays the same: easy to check and easy to undo.
For a new page
Create the “Workshops” page following the attached mockup. Put its styles in a CSS file of its own, loaded only by that page, so nothing else on the site changes while we adjust it.
A page under construction with its own CSS can go through many rounds without breaking the rest of the site. A one-off fix to an existing rule is made where that rule already lives.
From a static HTML site to a Velk theme
A site in plain HTML — a template you bought, an old static site, a layout exported to HTML — can become a Velk theme with the admin already filled in. Put the files in the project folder and ask; the skill's first stop is a plan for you to approve.
Ask the AI
Turn this HTML into a Velk theme. The files are in the old-site folder. Keep the look identical. The blog becomes a content type, the testimonials an editable list, and the menu and the footer contacts go to the options. Show me the plan before generating anything.
Saying how you want the content split brings the plan closer to what you need on the first try.
What the skill does
-
Sets the source aside
The original files go to a
_source/folder at the project root, outside the theme. If Velk isn't installed yet, it offers to install it and waits for your yes. -
Reads every page
Repeated header and footer become shared pieces, repeated cards a list or a content type, menu and contacts options, the texts page fields. It also collects the texts and images written in the HTML.
-
Shows the plan
Pages and their fields, content types, options and what the admin will come filled with. Nothing is generated until you approve it.
-
Builds and fills
It writes
site.json, the templates and the CSS; then a one-time script copies the old content into the database, so the admin opens filled in. -
Reports what's left
Images to move into the media library (until then the original files show), form recipients to set, tracking scripts (pixels, chat) to register on the Scripts screen, and
_source/to delete once you approve — the first deploy won't run while it is there.
Why a CSS change doesn't show
Velk's server rules (the .htaccess file) tell browsers to keep CSS and JavaScript files for a month. That makes the site faster, and it means a stylesheet always loaded from the same address keeps showing the old version to returning visitors — sometimes to you too. The fix is in the theme: each CSS and JS file is loaded with a version in its address, taken from the file's last change, so every change gets a new address that every browser fetches.
Themes the skill builds already do this, and the versioned publish warns when CSS or JS changed without it. For an older theme, ask once: “load the CSS and JS with a version in the address”.
Questions
Can the client change colors or fonts in the admin?
Not by default: the look is in the theme. If the client needs to switch something — a banner's color, a seasonal image — ask for an option the theme reads, such as a choice among the brand's colors.
I changed the CSS and the site looks the same.
If only you see the old version, reload ignoring the cache (Cmd/Ctrl+Shift+R in most browsers). If everyone does, the theme loads the CSS without a version in its address: ask the AI to add it.