Create a Client Presentation from Theme Assistant Changes

Outcome

By the end of this tutorial, you will know how to use SophMate for Theme Assistant client presentation while keeping the work reviewable inside WordPress.

Scenario

An agency has drafted homepage and product-page refinements and needs a concise client review before applying them.

What the image shows

The tutorial image shows Theme Assistant context: live preview, design controls, responsive review, and presentation-oriented workflow areas for visual changes.

Before you begin

• Confirm SophMate is active and the relevant module is available to your user role.
• Check provider, budget, and approval settings before asking SophMate to draft or execute work.
• Keep customer data, API keys, and private credentials out of prompts unless the workflow is explicitly designed to handle that context.

Guardrail

Use scoped CSS, responsive checks, accessibility review, and history notes before publishing visual changes.

Common mistakes to avoid

• Approving CSS after checking only the desktop preview.
• Using broad selectors that affect unrelated templates, checkout states, or mobile layouts.
• Skipping accessibility notes because the change looks visually small.

Step 1: Group changes by page and purpose

Separate header, hero, product card, checkout, and footer changes. Clients understand outcomes better than CSS selectors.

Step 2: Capture before and after states

Use preview snapshots or notes that describe what changed visually. Include mobile findings when the change affects layout.

Step 3: Include accessibility observations

Add contrast, spacing, tap target, and hierarchy notes. This turns the presentation into a decision aid, not just a cosmetic review.

Step 4: List approval status

Show whether each change is draft, proposed, approved, or applied. Clients should know what is waiting for their decision.

Step 5: Connect to next steps

End with the exact approval, revision, or implementation request needed from the client.

Review checklist

• Changes are grouped by page.
• Mobile and accessibility notes are included.
• Approval status is clear.

Success signal

The Theme Assistant workflow is successful when the change is scoped, reviewed at key breakpoints, accessibility concerns are documented, and the team can revert or explain the CSS history.

What to document

Document target page, selector or component family, desktop/tablet/mobile checks, accessibility notes, CSS history label, and approval status.

Owner and cadence

A designer owns visual intent, while the site owner or developer owns production impact. Review every meaningful CSS change before publishing.

Escalate when

Escalate when CSS affects checkout, account, accessibility, mobile navigation, or theme structure beyond the intended visual scope.

Related SophMate paths

• Features/Theme Assistant
• Features/Action Plans Approvals

Next action

Run this workflow on a low-risk example first. Once the result is easy to review and explain, decide whether it should become a repeatable playbook, workflow, watcher, agent, or documented team process.