Presentation purpose

Client presentation workflows help agencies show what changed, why it matters, and what review decision is needed. Keep the presentation focused on the proposed WordPress change, the affected pages, the expected user experience, and any risks.

Required context

Include before-and-after notes, responsive evidence, accessibility notes, approval status, and rollback options. The client presentation tutorial shows how to convert Theme Assistant work into a reviewable client artifact.

Client boundaries

Do not expose provider keys, internal prompts, private customer data, raw logs, or sensitive site configuration. If the client needs operational evidence, use diagnostics and support to prepare redacted details.

Owner and cadence

Primary owner: designer or developer, with site-owner approval for production visual impact.
Review cadence: before publishing, after theme updates, and after cache or WooCommerce template changes.
Escalate when visual work affects revenue-critical pages, accessibility, mobile navigation, or theme behavior outside the intended scope.

Production checklist

Include before-and-after context, affected pages, responsive evidence, accessibility notes, risks, and requested client decision.
Remove provider keys, internal prompts, customer data, private logs, and unrelated settings from presentation material.
Capture the affected URL, target selector, intended visual outcome, reviewer, and rollback note for every meaningful visual change.
Review mobile, desktop, keyboard focus, reduced motion, contrast, checkout, cart, account, and navigation behavior before publishing.

Acceptance checks

The client can approve, reject, or request revision without needing wp-admin access.
The agency can connect each slide or note to a real Theme Assistant draft or approval item.
The proposed CSS or presentation output can be traced to a specific page, component, and design goal.
The reviewer can reject, revise, or roll back the change without guessing which selectors were affected.

Common mistakes

Publishing broad CSS from a single preview without checking logged-out, mobile, checkout, account, and cache states.
Using external design references as production assets instead of review context.

Build the artifact with the client presentation tutorial.
Use Agency Governance for review ownership.
Use Responsive and Accessibility Review before visual publishing.
Use Client Presentation Workflow when an agency needs client approval.
Use Publishing and Rollback for Theme Changes before approving production CSS.
Use Multi-Page Consistency Checker before broad component updates.
Use Design Tokens and Style System before token-level changes.

Client Presentation Workflow