Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Everything in <prev plan>, includes:" shouldn't rely on the grid position. #91867

Closed
southp opened this issue Jun 18, 2024 · 5 comments
Closed
Assignees
Labels
2023 Pricing Page ⚡ Changes for pricing page optimisation 2023 [Type] Bug

Comments

@southp
Copy link
Contributor

southp commented Jun 18, 2024

To shorten the feature list, the plans grid puts "everything in , includes:" copy on top to emphasize that the higher-tier plan includes everything in the lower-tier one. However, it appears to rely on the grid position of a plan card rather than the logical order between these plans. There are three identified issues due to this:

1. The latest report from @niranjan-uma-shankar from pdvytD-EC-p2:

On a Creator site, the Entrepreneur plan shows "everything in Explorer" rather than "everything in Creator":

Image

2. On mobile, the copy is missing

See #90196

3. on tablet, the copy is missing for the left-most plan card in the 2nd row:

e.g.
Image

Image

@southp southp added [Type] Bug 2023 Pricing Page ⚡ Changes for pricing page optimisation 2023 labels Jun 18, 2024
@aneeshd16
Copy link
Contributor

Hi @southp, I think there are two possible solutions to this:

  1. We change the "Everything in.." text so that it will always refer to the previous plan and is not dependent on grid position:image
    This is a low-effort fix and can be done easily. However, if the text for the Entrepreneur plan reads "Everything in Creator, plus", it could be confusing as the features of the Creator plan are not listed on this page. Notably, the spotlight plan card does not have a list of features. This fix will make the grid appear "correct" but will not give the user any more clarity about plan features.

  2. We keep the "Everything in.." text as is so that it will always refer to the previous plan according to the grid position. We can make the text clickable so that it either expands into a dropdown or a modal listing the spotlight's plan features. We can also consider any other UI approach. Ultimately, it should give a clearer picture of the features of the previous plan on the grid.

@southp
Copy link
Contributor Author

southp commented Jun 21, 2024

Great points, @aneeshd16 . I'm thinking if we can actually combine the both, since a clickable "Everything in..." can also solve the particular issue of the 1st approach that the owned plan is not in the plans grid. If that's acceptable, we can first make it right, and then make it better :)

Is there other reason we should keep it as referring to the previous plan on the grid? Just curious to learn if there is any benefit that I'm overlooking.

@aneeshd16
Copy link
Contributor

I'm thinking if we can actually combine the both, since a clickable "Everything in..." can also solve the particular issue of the 1st approach that the owned plan is not in the plans grid.

That's true!

Is there other reason we should keep it as referring to the previous plan on the grid? Just curious to learn if there is any benefit that I'm overlooking.

I was thinking it would make it easier since users can scan the plans from left-right to view plan features, but I realized that it's not true for tablet and mobile.

Meanwhile, the PR is ready for review: #92016

@southp
Copy link
Contributor Author

southp commented Jul 2, 2024

@aneeshd16 I'm closing this issue since the accompanied PR has been launched. For the idea of the clickable "Everything in ...", should we create a follow-up issue for documenting the idea?

@southp southp closed this as completed Jul 2, 2024
@aneeshd16
Copy link
Contributor

Thanks @southp! Created a follow-up here: https://github.com/Automattic/martech/issues/3130

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2023 Pricing Page ⚡ Changes for pricing page optimisation 2023 [Type] Bug
Development

No branches or pull requests

2 participants