Write one Website request worth reviewing.
Name one change, its audience, the facts to retain, and the owner that should review the prepared work.
Follow the steps.
Use your own accurate details and check the result as you go. You can return to the relevant Website editor to make corrections.
Name one outcome
Say who the Page or Theme serves and what that visitor should understand or do.
Identify the owner
State whether the work belongs to a Page or Theme and name the supported destination.
Protect unchanged work
List facts to retain, files or content to preserve, and the human review that must happen before activation or publication.
Illustrative exampleWhat a useful result looks like
- The result
- A focused request naming the Page, facts to retain and intended visitor action.
- What to check
- Remove unrelated changes so you can judge one useful result.
Adapt the example to your Website and review the result before moving to the next task.
Keep the request reviewable
A focused request gives Composer a focused plan. It should identify the intended Website result without asking for unrelated product, API, or publishing changes.
State the decision after preparation
The Page or Theme owner reviews the prepared draft. Keep review, activation, and publication with the people responsible for that result.
Before you continue
Composer availability depends on the Website tool, permissions and AI credits. Reviewing this guide does not run a task, save a draft or publish a Page.