Pricing page polish

[agjohnson]

A few points that I accumulated from #166 for a second pass, eventually:

• [x] Hide feature list table on mobile, it looks awful stacked
• [ ] Set a min-height on the community/commercial plans tabs so that page content doesn't jump when switching tabs
• [x] Linking to either community/commercial tab should also focus the tab. Currently, it just switches the tab and doesn't scroll up
• [ ] Track enterprise contact us with analytics -- add a form somewhere to link to?
• [ ] Add commercial plan commentary back to each plan -- "good for private docs.." etc. See https://github.com/readthedocs/site-community/pull/166#discussion_r1022089972
• [ ] Do something different with community plan in feature listing? This is currently enabled, but under a feature flag of sorts.
• [ ] Consider potential reordered feature list, weigh sorting by plan vs sorting by feature category and context -- https://github.com/readthedocs/site-community/pull/166#discussion_r1022097270
• [ ] Location of single line community plan callout -- above or below plan listing? This was originally more of a toast at the top of the page
• [ ] Mobile table sticky header row doesn't scroll horizontally. Probably just still remove the table on mobile entirely
• [ ] Highlight feature table column in some way when linking from plans above

[humitos]

I'm not sure if this effect is on purpose or not, so, I'm commenting here.

When I click on the "Pricing" link, it goes to the pricing page and automatically scrolls down to the pricing table. Which I find a little "aggressive" (not sure if that's the correct word) --but I personally don't like the page moving it automatically by itself.

[agjohnson]

Ah good catch, this is a regression from earlier on in my work. It's not intended, the JS that controls this probably should track user actions more aggressively. I'll treat this issue as a bug and get a fix out

[humitos]

Would it be possible (and useful?) to highlight the column of the specific plan when we click "See all features"?

[agjohnson]

Yeah, this would be possible, it waffled on putting this in the first iteration. It would be a good addition, but might take some custom code. I'll note this above though :+1: