Build and refine your website

The conversation is where changes begin. Preview shows the result. Code shows the underlying site files for advanced edits.

The page selector chooses the page in the preview. Desktop and Mobile change its width. Photos, History, and Domains open their own panels.

1. Open the site from the dashboard.
2. Choose a page in the page selector.
3. Select Preview to inspect it, or Code for a source edit.
4. Open the site menu for Site overview and project actions.

On narrow screens, some controls move into the site menu. Site overview opens Hosting, where forms, posts, SEO, and other settings live.

Name the page, the desired result, and the facts to preserve. Work through one meaningful change at a time.

1. Supply exact wording for names, prices, and contact details.
2. Review the result before requesting the next change.
3. Use the stop control if the request is going in the wrong direction.
4. Explain the correction before starting the next request.

On the Services page, add a section for seasonal garden cleanup.
Use this price: starting at $180 after an assessment.
Keep the existing colors and contact form.
Add a Request a quote button that reaches the form.
Check the result on a phone-sized screen.

AI can make mistakes. Review business claims and test controls before publication. Never paste passwords or secret API keys into chat.

Ask Launch to add a page for a distinct service, project, or customer need. Include its purpose and the link that should reach it.

1. Name the new page and describe the information it needs.
2. Ask for a suitable address and links from the main navigation or relevant pages.
3. Select the new page in Preview.
4. Test the links that lead to it and its main contact action.
5. If an old address changes, add a redirect before publishing.

• Search details and redirects

The editor saves draft changes automatically. The save indicator shows whether the current changes reached the server.

Publishing is a separate action. A saved draft does not change the public website until publication succeeds.

1. Wait for the saved status before closing the editor.
2. Keep the tab open if the save fails. Check the connection and follow the displayed recovery action.
3. Review the draft, then select Publish when it is ready for visitors.

If another tab or collaborator changes the site, follow the conflict message. Do not assume that an unsaved local edit replaced the newer version.

• Publishing and version recovery

Code exposes the site's files. It is optional for ordinary content and design changes.

A source change still needs to pass the site's checks. It can also affect mobile layout, accessibility, or external services.

1. Save the current version before a substantial source change.
2. Change only the files needed for the task.
3. Resolve the displayed errors and inspect Preview.
4. Test the affected pages before publishing.

Use Environment variables for secret service keys. Custom code and site files reach visitors and must not contain secrets.

• Connect services safely