Clarifying questions
When your brief leaves something important open, PageFork asks before it builds instead of guessing.
Sometimes PageFork will stop and ask you a question instead of building straight away. You’ll see it in the chat as a small panel with a question and a few options to click.
This is deliberate. A quick answer costs you a few seconds; a whole site built on a wrong guess costs a rebuild.
Answering
Click one of the options and PageFork carries on with that answer. The option’s label is sent back as your reply, so it appears in the conversation like any message you typed.
You can also type your own answer in the box instead, if none of the options fit. Say whatever you’d have said in a normal message — you’re not limited to the choices.
Once answered, the question panel collapses and marks which option you chose. Expand it again any time to see what was asked.
Only the most recent unanswered question accepts input. Older ones are history.
When you’ll see questions
Creating a new site — often. This is where a wrong guess is expensive, so PageFork leans towards asking one question at the very start, before writing any files. Expect it when your brief leaves open:
- Facts it would otherwise have to invent — business name, location or service area, contact details, existing brand colours.
- A major direction — is the site primarily for taking bookings or showcasing work? What overall style? One page or several?
It asks one question, folding in the single most important gap, and usually marks the option it would have assumed anyway — so clicking the default is always a reasonable move.
Editing an existing site — rarely. Most edit requests just get done. PageFork only asks when a request is genuinely ambiguous in a way that changes the outcome: conflicting instructions, missing essential content, or two very different plausible readings. It won’t ask you to confirm work it can already do, or to settle minor styling choices.
It never asks mid-build
Once PageFork has started creating your site, it won’t stop to ask anything. A question at that point would leave you with a half-built site, so instead it finishes with sensible assumptions and you adjust afterwards.
That’s the normal way to work anyway — see Iterate in small steps.
Avoiding questions altogether
If you’d rather not be asked, put the answers in your brief. A prompt that already names the business, the goal, and the style gives PageFork nothing to ask about.
Writing great prompts covers what’s worth including.