Build a new WordPress website here: install WordPress with wp-install, make a
custom theme that fits the business (no template look) and set up the pages
and the menu.
For: De Rugzak physiotherapy, a practice in Assen.
Purpose: show patients what we do and let them request appointments.
Pages: Home, Treatments, Prices, Team, Contact.
Features: Contact form, Opening hours and address, Reservations or appointments.
Nobody typed that request. The start wizard in the Invoker Assistant put it together from five steps of clicking and filling in. That is the whole point of the wizard: it asks exactly the things an assistant needs in order to keep building without stopping for questions, and turns your answers into a request you can still edit before anything happens.
Where do you find the wizard?
In DirectAdmin, open the Invoker Assistant and pick the website that is still empty. The start screen of an empty website shows three buttons:
- New website → opens the start wizard.
- Install WordPress (labelled "recommended") skips the questions and sends the install request straight away.
- I would rather type takes you to the empty chat bar.
You want the wizard when you want more than a bare WordPress install: a theme that fits your business, the right pages, and the features you actually use.
Step 1: new or move
The first question is "What do you want to do?" with two choices: create a new website, or move an existing website. Both routes end at the same editable request, but the questions in between differ. Pick moving and it is three steps instead of five.
Step 2: what do we build with?
Three options:
| Choice | What for |
|---|---|
| WordPress (recommended) | You want to edit texts and photos yourself in an admin area, with plugins, a blog or a shop. |
| Static website | A one-pager or a few pages. Fast and simple; changes go through the assistant. |
| Next.js (React) | An app-like site, built as static files. Only if you know why you want this. |
For most businesses WordPress is the right choice, which is why it carries the "recommended" label.
Step 3: tell us about your website
Now the content questions. Three text fields and two rows of clickable labels:
- Business or topic, for example "Jansen Bakery, artisan bakery in Haren".
- Purpose of the site, for example "show customers what we sell and let them reserve bread".
- For whom, for example "people from Haren and surroundings".
- Pages: Home, About us, Services or products, Contact, Prices, Team, plus a field for other pages.
- Features: contact form, opening hours and address, blog or news, web shop, reservations or appointments, photo gallery, reviews, newsletter, FAQ, multilingual.
Be as concrete as you can here. Anything you leave out, the assistant has to invent later or come back to ask you about.
Step 4: look and feel
This step is about how the site should look:
- Style: business and clean, warm and personal, playful, luxury, minimal, or "let the assistant choose".
- Language of the website: Dutch, English, or both.
- Colours, logo, font, for example "warm yellow and brown; the logo is in images/logo.png".
- Websites you like: links, with a few words on what appeals to you.
- Texts and photos: have example texts written that you adjust later, use what is already there, or supply them yourself.
That last field decides whether half an hour later you have a site with real text in it or a site full of blank spots. Pick "write example texts that I adjust later" if you have nothing ready yet.
Step 5: check the request
The last step no longer asks a question. It shows a text box with the complete request assembled from your answers, above it the line: "This is the request. Adjust what you like and click Start building."
Read it properly. This is the moment to add something that fit in no field, for example "the opening hours have to be on the home page" or "do not use a sliding carousel". The request already ends with the instruction to first show the plan briefly, then build, check the result with screenshots on desktop and mobile, and put the key facts in the notes about the website.
Click Start building and the request goes into the chat as your first message.
And if you are moving an existing site?
Pick moving at step 1 and the wizard asks how:
- From a git repository: you fill in the repository and the site gets linked, so every push goes live.
- The files are already on this website: you uploaded them over FTP or with the file manager, and the assistant checks paths, permissions, PHP version and database.
- From another host: you fill in the current address and the current host, and the assistant explains step by step what it needs from you.
After that you pick the kind of site (WordPress, static, PHP, Next.js or "not sure") and get the same editable request. When moving, the request automatically includes making a backup first if anything is already on the website.
Common mistakes
"I do not see the New website button." The wizard belongs to the start screen of an empty website. If a site is already in the folder, you simply start in the chat with what you want changed.
"I left everything blank and clicked Start building anyway." Then the assistant builds on assumptions. In auto mode it does not stop to ask, so you get a site with invented names and hours. Go back with Back and fill in at least the business, the purpose and the pages.
"I still wanted to edit the request but had already clicked through." In the text box of the last step you can rewrite everything; it is plain text. And even after that you can undo each task separately, see What if the assistant stalls or gets stuck.
"The wizard ticked a web shop but no web shop appears." The features go into the request as a list, not as a guarantee. A web shop is work for its own request afterwards. Tick what the site has to do, then ask for the big features one by one.
"Can I do this with Codex?" Yes. The wizard belongs to the assistant, not to a provider. The assembled request works the same with Claude or Codex connected; see Choosing Claude Code or Codex.