How it works
Open any page of your sitebuild from the dashboard. You'll see the current preview on one side and a chat panel on the other. Type the change you want in plain English:
- "Move the testimonials section above the pricing section."
- "Make the CTA button green and add a small note underneath that says 'no credit card required'."
- "This page needs a third feature card. Use the same style as the existing two."
- "Replace the body copy in the hero with: …"
Wyvid regenerates the affected page, the preview updates, and the underlying HTML is kept consistent across the rest of the build. Your CSS variables, brand tokens, and shared components stay aligned — change a color in one place and it propagates.
Why this is the actual product
Anyone can hack together a one-shot generator. The reason teams keep using Wyvid is the iteration loop. Real client work is twenty rounds of "can we move this, change that, add another section" — and that loop is where most generators stop being useful. Wyvid is built for that loop.
Scoped changes
You can scope a request to one page or apply it across the whole site. "Make this page's hero taller" affects only that page. "Use this typeface for all headings" applies globally. Wyvid asks if it's unclear which scope you meant.
You stay in control
Every iteration is saved as a new revision. You can compare against earlier versions, roll back, or branch. Wyvid never overwrites your previous work without an explicit revision step.
Good prompts vs vague ones
The model is sharper when you're specific. "Make the pricing section feel cleaner" produces something — but "Reduce the pricing card padding by ~25%, drop the gradient background, and align prices to baseline" produces exactly what you wanted. Wyvid's chat works best as a junior collaborator: clear instructions, fast turnaround.