Edit vs Discuss
When to ask PageFork to change your site, and when to just talk.
The composer has two modes: Edit (the default) and Discuss. They look the same, but they do very different things.
Edit
In Edit mode, PageFork treats your message as an instruction to change the site. It will:
- Read the relevant pages of your site.
- Plan the change.
- Write updated code.
- Produce a new version that appears in the preview.
Every Edit message creates a new version. Undo rolls it back without losing your chat history.
Use Edit when you know what you want changed:
- “Make the hero darker.”
- “Add a three-column feature section below the hero.”
- “Rewrite the CTA on the pricing page.”
Discuss
In Discuss mode, PageFork answers questions and brainstorms with you without touching the site. It can:
- Explain what’s on your site.
- Suggest what to try next.
- Help you decide between two approaches.
- Rewrite copy in chat for you to review before committing.
No version is created. The preview doesn’t change.
Use Discuss when you’re thinking, not yet deciding:
- “What sections does my homepage have?”
- “Give me three headline options for the hero.”
- “Would a FAQ or a comparison table be better here?”
Credits
Both modes consume credits, but Discuss is usually cheaper because it doesn’t rewrite your site — it just reads and responds. When you’re exploring ideas, Discuss is the efficient mode.
Switching modes
Below the composer you’ll see an Edit / Discuss toggle. It sticks for the current session, so if you switch to Discuss to brainstorm, remember to switch back to Edit when you’re ready to make changes.
Which should I use?
| Situation | Use |
|---|---|
| Clear, specific change | Edit |
| Generate options to choose from | Discuss |
| ”What should I do about X?” | Discuss |
| Apply the option you just picked | Edit |
| Fixing a small issue | Edit |
| Exploring a big structural change | Discuss first, then Edit |