Multi-Page Consistency Checker

When to run it

Use the consistency checker when a change affects repeated patterns such as headers, product cards, buttons, notices, checkout helpers, account sections, or footer blocks. A single polished page is not enough when the same component appears across the storefront.

Review scope

Compare representative pages before asking for CSS: homepage, archive, product detail, cart, checkout, account, and any campaign landing page. The checker should identify drift in tokens, typography, spacing, component density, responsive behavior, and accessibility risk. Pair this with responsive accessibility review when mobile or keyboard behavior may change.

Approval output

The final note should explain which pages were checked, which differences are intentional, which differences need design decisions, and which CSS changes remain scoped. Use client presentation workflow when the consistency review needs client approval.

Quick reference

• Use this page when planning, reviewing, presenting, publishing, or rolling back Theme Assistant visual work.
• Do not treat generated CSS, external references, or polished previews as production-ready until responsive, accessibility, cache, and rollback checks pass.
• Key decision: whether the visual change is scoped, reversible, accessible, and safe on revenue-critical templates.

Scope limits

• Do not use this page to approve copying protected assets, broad selectors, or design changes that bypass accessibility and checkout/account review.
• This page does not replace development review for PHP templates, checkout logic, plugin behavior, or structural theme changes.
• Use it for scoped visual review, presentation, and rollback discipline before production CSS changes.

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 repeated components drift across checkout, account, product, campaign, or navigation pages and the intended standard is unclear.

Access and data boundary

• Visual-review evidence should name the target URL, selector or component family, viewport, accessibility finding, and rollback label without exposing unrelated admin data.
• Use public URLs, safe screenshots, component selectors, breakpoints, and design notes that can be reviewed without exposing private admin or customer context.
• Keep checkout payment details, account data, private staging URLs, and client-only design files out of prompts, fetched references, and presentation notes.

Production checklist

• Select representative pages for every repeated component family before asking Theme Assistant for a consistency recommendation.
• Document which differences are intentional and which require a design or approval decision.
• 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

• Repeated components are reviewed across homepage, archive, product, cart, checkout, account, and campaign contexts where relevant.
• The output separates token drift, layout drift, accessibility risk, and intentional page-specific differences.
• 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.

Failure modes to test

• Test blocked reference URLs, unsafe copied assets, mobile breakage, accessibility regressions, checkout/account side effects, and rollback from the wrong CSS entry.
• Test mobile overflow, contrast failure, keyboard focus loss, reduced-motion behavior, broad selector impact, cache differences, and checkout/account regressions.
• Confirm the CSS or presentation workflow can be rejected, revised, or rolled back from a named history item.

Evidence to capture

• Capture before/after screenshots, affected breakpoints, accessibility result, CSS history label, and rollback confirmation.
• Capture target URL, selector or component family, desktop/tablet/mobile review, accessibility notes, CSS history label, and approval status.
• Record screenshots or presentation notes only after removing provider keys, customer data, private URLs, and unrelated admin details.

Decision record

• Decision field to include: target template family, affected breakpoints, accessibility result, client or site-owner approval, and rollback label.
• Record the visual decision, target URL, component or selector family, reviewer, accessibility result, responsive result, CSS history label, and rollback owner.
• Include whether checkout, cart, account, logged-out, cache, reduced-motion, and mobile states were reviewed before production publishing.

Stop or rollback path

Stop visual publishing when scope, accessibility, mobile behavior, checkout/account impact, or rollback history is unclear. Revert the named CSS history item when needed and resume after affected pages are rechecked.

Monitoring window

• Monitor affected pages after cache clears, theme updates, mobile traffic, and checkout/account review.
• Review visual feedback, accessibility findings, and CSS history before expanding the design pattern.

Expansion criteria

• Visual changes can expand only after checkout, account, product, navigation, mobile, accessibility, and rollback checks pass.
• Reuse the design pattern only after affected breakpoints, templates, accessibility states, and rollback history pass review.
• The designer and site owner agree which pages or component families are in scope.

Common mistakes

• Checking only the homepage and missing product, cart, checkout, account, or campaign variants of the same component.
• 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.

Common questions

When is a visual change ready to publish?

Publish only after scope, affected templates, responsive behavior, accessibility, checkout/account impact, cache behavior, approval status, and rollback history are clear.

Who should own this decision?

The designer should own visual intent, while the site owner or developer approves production impact.

What should stop the rollout?

Stop when visual work affects checkout, account, mobile, accessibility, cache, or broad selectors without a rollback note.

Related operations

• Use Publishing and Rollback for Theme Changes before approving production CSS.
• Use Design Tokens and Style System before token-level changes.