SiteSparkSiteSpark星火建站type a prompt · ship a website
← All posts
How-to

Editing a site by talking to it: how to ask so the page actually changes

Editing is far cheaper than regenerating, if you ask well. Here is the three-part shape of a good request, five before-and-after examples, and when to start over instead.

Editing versus regenerating

Regenerating starts from zero: the parts that were already right — product data, page structure, backend logic — go with it, and you pay twice.

Editing changes the code you already have, at the one place you name. Real projects come out of three to five rounds of this, so treat editing as the process rather than as a rescue.

Three parts of a good request

Name the place, describe the result, state the constraint:

  • Place: which page, which block, which element — "the hero on the homepage" beats "the homepage"
  • Result: what it should look like afterwards. "Filter without reloading the page" beats "improve the filter"
  • Constraint: what must not change — "leave the other pages alone", "do not touch the schema"

Five before-and-after examples

The left version costs you three rounds; the right one lands once:

  • "The page looks bad" → "the hero is crowded: make the featured products three cards in a row and drop the heading one size"
  • "Change the colours" → "deep navy background, off-white text, orange buttons — colours only, no layout changes"
  • "Add a feature" → "add filtering to the catalogue by pet type (dog/cat) and price, without a full page reload"
  • "It is broken on mobile" → "at 375px the product cards overflow: make it one column with full-width images"
  • "Ordering does not work" → "the buy button does nothing: check the click handler and whether the order endpoint is called, then tell me what you changed"
Add a sticky buy bar at the bottom of the product page, visible while scrolling, mobile only
Make checkout one column: delivery details, then payment, then total and the pay button
Reduce the nav to Products / About / Contact and move the rest into the footer

When to regenerate instead

Editing is for local changes. Start over when:

  • The direction is wrong (a brochure came out of a store request)
  • The target has to change (a static site must now store data and take money)
  • Three rounds have failed on the same problem and each fix broke something else

How to verify an edit

Reload first, then check three things:

  • The thing you asked for actually changed
  • Everything you did not mention is untouched — especially entered data and buttons that already worked
  • It still holds on a phone, where most of these problems actually appear

Idea → website

Your next website is one sentence away.

Stop scaffolding. Start describing. Build, run, and ship a real website without leaving the conversation.