Step 0: Gather what you already have
Before you write anything, collect what only you can supply: your copy or a rough draft of it, your logo, photos, brand colors and your real contact details.
You can attach all of it to a message. In Veloxa Build each file (images, a PDF, a CSV or a text file) is saved in the project's assets folder and used where you ask, so the first version can carry your real content instead of placeholder text.
No copy yet? Say in one line what each section should say and edit the draft it writes. Reacting to a draft is easier than writing from nothing.
Step 1: Describe the site
Three things do most of the work: what the site is for, who it is for and which sections it needs. Design adjectives matter far less than people expect. The example, in full:
Build a one-page site for a two-person landscaping business in Portland. Sections: a hero with the business name and a “get a quote” button, services with rough price ranges, a gallery of past work, a short about section with a photo of the two of us, testimonials, the area we cover, and a quote request form that asks for name, address, phone and what they need. Send each quote request to my inbox. Warm and outdoorsy, easy to read on a phone.
The section list is the important part: it gets you the right shape on the first try, and shape is the tedious thing to fix later. Two words of tone (“warm and outdoorsy”) beat a paragraph of styling.
The line about the inbox is deliberate. Forms on a published site send what visitors type to the site's inbox, with an email to you for each submission, so putting the form in the first version tells you at once whether it works.
Step 2: Fix structure before appearance
When the first version appears, check the skeleton before the colors. Structural changes undo cosmetic ones.
- Are the sections right, and in the right order? Reordering is one sentence.
- Is the main action obvious? For a business site that is usually one call to action, at the top and the bottom.
- Does it read on a phone? Narrow the preview; most visitors will see this width.
- Is anything missing a visitor would look for? Hours, area covered, prices, whether you come to them.
Step 3: Then the appearance
Once the structure holds, switch from writing to pointing. Turn on click-to-edit, click the exact thing you mean and describe the change: “this heading is too big on mobile”, “more space above this section”, “the same green as the logo”.
Changes that touch the whole site are still better said than clicked: “use a warmer off-white background throughout and loosen the line height on body text”. Every change is a version, so a tweak that misses is easy to undo.
Step 4: The parts that do something
A site stops being a brochure when it needs to remember something. These are ordinary requests:
- Forms that keep submissions. “Send every quote request to my inbox.” Each organization can receive 100 submissions a month on Free and 5,000 on Pro, with spam protection built in.
- Content you change in a sentence. “Raise hedge trimming to the new price and add gutter cleaning.” Then publish the change.
- Sign-in with per-person data. “Add a sign-in button so returning customers can save a plant wish list.” Each person sees only what they saved.
What it does not do: take payments, sync a booking calendar or send email to your visitors. AI features you add work while you build and test; AI for the visitors of a published site is not available yet. The trade pages spell out these limits for each kind of business.
Step 5: Ask for the search basics
A generated site is plain HTML, so the content is in the page a search engine reads. What it will not always do unprompted is the metadata, so ask: “give each page a unique title and description, add Open Graph tags using the hero image, add structured data for a local business with the address and opening hours, and give every image a descriptive alt text.”
Then check by hand that your titles read like something a person would click, not a keyword list. That judgment is yours.
Step 6: Publish
Before publishing, use Share draft to send the work in progress to a partner or client; anyone with the link can open it. When you are ready, Publish puts the site on an address like yourname.veloxa.site with HTTPS, in one click. Later edits stay in your draft until you choose Publish changes.
Custom domains for Veloxa Build sites are coming soon (1 on Starter and 5 on Pro). Until then a published site lives at an address like yourname.veloxa.site, with HTTPS. If you need your own domain today, you can download the project and host the files on VeloxaHost hosting, but Forms and their inbox work only on veloxa.site, and sign-in, file storage, the database and AI features call Veloxa Build's services rather than anything in the zip, so test them on the new host and plan to replace them if you leave.