Prepare Theme changes for review.
Describe one style direction, identify affected Page patterns, and inspect the Theme candidate before it can become live.
Build around this situation.
Use your own accurate details and check the result as you go. You can return to the relevant Website editor to make corrections.
Name the style direction
State the type, color, shared-part, or other supported Theme change and the Website it affects.
Choose Page patterns to check
Identify a service Page, content-heavy Page, header, footer, or other real pattern that should be inspected.
Review the candidate
Open Theme & styles, compare the candidate with the request, and keep activation separate from publication.
Illustrative exampleWhat a useful result looks like
- The result
- A Theme draft or candidate you can inspect against the requested direction.
- What to check
- Check shared parts, typography and small-screen behavior before activation.
Adapt the example to your Website and review the result before moving to the next task.
Keep shared and Page decisions clear
A Theme can change supported shared presentation. Page-specific copy, images and Forms continue to belong to their own owners.
Do not skip the inactive state
A Theme candidate is an editable result for human review. Keeping or activating it requires the existing Theme controls and evidence.
Before you continue
Composer is not currently enabled for general use. A prepared Theme candidate does not become the active Theme or a Marketplace listing automatically.