Size, color, sale, stock, mobile
Problem: shoppers need fast narrowing without losing the product grid on mobile.
- ProofColor swatches, size buttons, chips
- Feature setAttributes, stock, sale, mobile drawer
- CTADemo: fashion storefront
Use cases
Help visitors recognize their own catalog.
Buyers rarely ask for "a filter plugin" in the abstract. They ask whether it works for fashion sizes, electronics brands, B2B parts, large catalogs, or SEO-controlled filtered pages.
- Fashion
- Electronics
- B2B parts
- Large catalog
- SEO catalog
Scenario library
Each use case should connect problem, proof, and setup path.
These cards can become detail pages later. For MVP, one page with strong sections is enough.
Brand, rating, budget, fuzzy search
Problem: shoppers compare many specs and need search plus structured facets.
- ProofBrand filter, rating, price slider
- Feature setSort, fuzzy search, Step Filter
- CTADemo: electronics finder
Compatibility and conditional paths
Problem: buyers need guided product choice, private products, and compatibility logic.
- ProofCustom taxonomies and conditions
- Feature setStep Filter, role scenarios, stock
- StatusStep Filter Free/Pro pending
Counts, empty values, index, cache
Problem: long attribute lists create dead ends and slow count calculations.
- ProofHide empty, grey out, show more
- Feature setCount modes, index, cache, rebuild
- CTADocs: optimize large catalogs
Clean URLs without index chaos
Problem: filters can create duplicates unless URL and index rules are controlled.
- ProofURL preview and selected chips
- Feature setCanonical, noindex, selected params
- CTADocs: configure SEO URLs
Repeatable client setup
Problem: each client theme has different selectors and support expectations.
- ProofCompatibility checklist
- Feature setImport/export, debug, selectors
- CTACompatibility page
Content pattern
What each future detail page should contain.
Use this repeatable structure when turning a card into a standalone SEO or campaign page.
| Section | Content | Why it matters |
|---|---|---|
| Problem | Catalog-specific pain in plain WooCommerce language | Creates recognition quickly |
| Proof | Demo state, product grid, chips, URL, count, or mobile drawer | Turns claims into visible behavior |
| Setup path | Relevant feature groups and docs links | Shows the route from interest to implementation |
| Commercial note | Plan/Pro note only when confirmed | Avoids misleading freemium claims |