Changing your site
You don't edit code or drag boxes around: you say what to change, in the same chat, and rwaft builds the new version.
Send a follow-up
In the chat where the site was built, describe the change: “make the header darker”, “add a contact page”, “change the latte to $4”.
Each follow-up is a complete build and costs the same as the first, 1 credit, however big the change.
rwaft remembers what you asked for before, so you only describe what's different.
Every version gets a new link
A change publishes the new version at a new link. Share the latest one, and update it anywhere you've posted it, like your bio or a QR code.
Changes work for a day
rwaft keeps a site's code for a day after each build, and follow-ups edit it within that time. After that, describe the whole site again and rwaft builds it fresh.
To keep the code for good, push it to GitHub.
Tips
- One or two changes per message are easier to check than ten
- Say where: “the button in the first section”, not just “the button”
- If a change isn't right, describe what you want instead; there's nothing to undo first