Pricing Plans Page Design cleanup

[scottjehl]

Here's a round of cleanup for some of the design treatments on the Pricing page, with a goal of better grouping and hierarchy of what we're offering, as well a little better design parity with layouts elsewhere.

Desktop Layout:

Smallscreen layout:

Additionally, we can bring just the Plan Chooser (annual/monthly) over to the Account page too, for consistency:

Some Notes:

• The top nav should have an active state on Pricing. You can add a class and tabindex to the anchor:
• I've brought the price callout in the signup-hed-contain header down to 1.3em or so font-size, and also wrapped the "/mo" text in an em (or whatever) to set it smaller at font-size .8em, font-weight 500, and normal font-style.
• On small screen, the gradient in the header is adjusted to have a steeper slant. Something like this should do the trick below a certain breakpoint threshold: .signup-hed-contain { color: white; background-color: #6b25cf; background-image: url(/images/src/white-swoop.svg), url(data:image/svg+xml,%3Csvg ...%3E); background-position: bottom -15px left 100%, bottom 0 left 100%; background-repeat: no-repeat, no-repeat; background-size: 250%, cover; display: flex;}
• The Global footer needs to be included like other pages.

[scottjehl]

A few things from up top that are remaining:

• On small screen (below 40 em viewport or something?), the gradient in the header is adjusted to have a steeper slant. Something like this should do the trick below a certain breakpoint threshold: .signup-hed-contain { color: white; background-color: #6b25cf; background-image: url(/images/src/white-swoop.svg), url(data:image/svg+xml,%3Csvg ...%3E); background-position: bottom -15px left 100%, bottom 0 left 100%; background-repeat: no-repeat, no-repeat; background-size: 250%, cover; display: flex;}
• The Global footer needs to be included like other pages. Maybe this is a template issue with all pricing and account things?
• Design for account upgrades:
  

[github-actions]

We're in the process of cleaning up issues on this project in order to ensure we're able to stay on top of high priority bugs and feature requests. As a part of this process, we're automatically closing any issues that have had no activity within the last two years, including this one, since the codebase has changed dramatically in that time. If you feel this is still relevant, please file a new issue using the relevant issue template so we can get it prioritized. Thanks!