Skip to content

A4A POC: Pressable Name Changes (UI only) - #113957

Draft
jeffgolenski wants to merge 1 commit into
prototype/msd-marketplace-hostingfrom
visual/pressable-plan-rename
Draft

A4A POC: Pressable Name Changes (UI only)#113957
jeffgolenski wants to merge 1 commit into
prototype/msd-marketplace-hostingfrom
visual/pressable-plan-rename

Conversation

@jeffgolenski

@jeffgolenski jeffgolenski commented Aug 31, 2026

Copy link
Copy Markdown
Member

Part of the Pressable plan rename exploration. Builds on #113804.

Proposed Changes

CleanShot 2026-08-31 at 17 38 35@2x CleanShot 2026-08-31 at 17 36 01@2x
  • Visual-only exploration of Pressable's upcoming plan rename — Signature and Premium become Standard, Agency, and Performance — applied across both the current marketplace (client/a8c-for-agencies) and the prototype marketplace in the Multi-site Dashboard (client/dashboard).
  • Each dashboard gets one temporary pressable-plan-display-names.ts that maps catalog slugs to the proposed names and to the proposed tier grouping. Components read names through it, so deleting the two files and their imports reverts the whole exploration.
  • Current marketplace: the three plan tabs are re-cut rather than relabelled — Standard covers the plans at 1, 3, 5 and 10 installs, Agency covers the thirteen from 20 through 500, Performance covers the eleven former Premium plans plus Performance Custom. Slider stops, plan card title, cart button, and the tier body copy follow the new grouping.
  • Dashboard marketplace: the "Choose a plan type" cards become Standard, Agency and Performance, with the plan dropdown, right-rail summary, cart labels and order summary all reading the proposed names.
  • No changes to product slugs, plan IDs, prices, entitlement numbers, cart or checkout logic, API calls, or analytics event names. No files, variables, CSS classes or test IDs renamed.
  • Not intended to merge — this is a throwaway branch for design review, to be screenshotted and discussed before any of it is specified for real.

Why are these changes being made?

Pressable is replacing the Signature and Premium tiers with Standard, Agency and Performance, and the sub-tier numbers become site counts, so the numbering does not carry over one for one. Rather than describing the change in a doc, this puts the proposed names into both live marketplaces so the team can see what actually breaks visually — where tier boundaries no longer match the tabs, where copy names a tier, and how much of the surface area is affected.

Two things surfaced that need a decision before this becomes real work:

  • There is no Enterprise tier in the new structure, and Custom now sits under Performance. In the dashboard marketplace the three cards are Standard / Agency / Performance, where Performance absorbs today's Custom card (sales-assisted, no plan picker) and the former Enterprise plans at 200–500 installs move up into Agency. The consequence worth discussing: "Performance" then means a family of eleven numbered plans in the current marketplace, but a contact-sales route in the dashboard one.
  • The two dashboards do not carry the same catalog. The current marketplace has the Signature 1–17 and Premium 1–11 plans the rename table is written against. The dashboard prototype still carries the legacy Build/Growth/Advanced/Pro/Business/Enterprise lineup. Both share the same install ladder (1, 3, 5, 10, 20 … 500) and the new sub-tier numbers are site counts, so the mapping was matched on install count there — worth confirming that assumption is the intended one.

Known gaps: the existing-customer slider logic in the current marketplace still keys off the old category boundaries, so an agency with an existing plan may see an odd minimum stop; and the Agency tab opens on Agency 200 rather than Agency 20, because that tab's default plan is unchanged.

Testing Instructions

Run one dev server at a time — both share public/evergreen and build/, so running them together produces 503s on half the chunks and a blank page.

Dashboard marketplace:

  • yarn start-dashboard
  • Open http://my.a4a.localhost:3000/marketplace/hosting and select the Pressable tab.
  • Switch between the Standard, Agency and Performance cards; check the plan dropdown, the right-rail title and its cart button.
  • Add ?existing to the URL to check the returning-customer header and the "Upgrade to …" button.

Current marketplace:

  • yarn start-a8c-for-agencies-p
  • Open http://agencies.localhost:3002/marketplace/hosting/pressable
  • Switch between the Standard, Agency and Performance tabs; check the slider stops, plan card title, cart button and the "With … plans" line.
  • Toggle "Refer products" in the header and open the Performance tab to see the eleven Performance plans; click the More stop on the Agency tab to see Performance Custom.

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • For UI changes, have you tested the affected components in dark mode?
  • Have you tested accessibility for your changes?
  • Have you used memoizing on expensive computations?
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?

🤖 Generated with Claude Code

Throwaway, display-only exploration for design review. Renames Pressable's plan
tiers in both marketplaces and re-cuts the tier groupings, without touching
slugs, product IDs, prices, entitlements, carts, API calls, or analytics.

Each dashboard gets one temporary `pressable-plan-display-names.ts` mapping
catalog slugs to the proposed names and tiers; components read names through it,
so deleting the two files and their imports reverts the whole exploration.

Not final, not shipping.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant