feat(customer-portal): redesign plans page cards - #9
Merged
Conversation
- Collapse duplicate monthly/annual plan cards into a per-product billing interval toggle, defaulting to the interval of the active subscription - Restyle plan cards as standard SaaS pricing tiles: elevation, hover lift, hero price, divider, checkmark feature list parsed from the description - Equal-height cards with full-width CTAs pinned to the bottom so buttons align across a row - Mark the current plan with a blue ring and chip instead of a filled card Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Visual redesign of the customer-portal plans page (
/customer-portal/:token/plans), which was rendering as a long wall of uneven boxes.$19not$19.00), and plan names drop the now-redundant(Annual)suffix.Notes
getIntervalTranslationKeymap from~/core/constants/form.plan.description(lead-in, em-dash, comma-separated list). Descriptions that don't fit that shape fall back to a plain paragraph. If we want this durable, the follow-up is afeatureskey in plan metadata.Test plan
tsc --noEmitandpnpm lintclean🤖 Generated with Claude Code