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

LITS: The theme grid clearly marks required upgrades but theme details doesn't #96162

Open
dsas opened this issue Nov 7, 2024 · 9 comments · May be fixed by #98451
Open

LITS: The theme grid clearly marks required upgrades but theme details doesn't #96162

dsas opened this issue Nov 7, 2024 · 9 comments · May be fixed by #98451
Assignees
Labels
Good First Issue Small, contained issues. [Pri] Normal Schedule for the next available opportuinity. [Status] Escalated to Product Ambassadors [Status] Needs Design Add this to PRs that need input from Design [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended

Comments

@dsas
Copy link
Contributor

dsas commented Nov 7, 2024

Quick summary

It's not clear on the theme details page of a non-free theme what upgrade is required and how much it's going to cost.

Grid Details
Image Image

Steps to reproduce

  1. Select a Free site
  2. Go to Appearance → Themes in the menu
  3. Notice that many themes have a premium indicator, when hovered it says that you need a certain plan.
  4. Click on one of the themes

What you expected to happen

I expected the theme details page to be at least as clear that an upgrade is needed and to which plan. Ideally it would also mention the price.

What actually happened

The theme details page doesn't show which upgrade is required, the main CTA is "Upgrade to activate" so it is clear that something is needed. But not what, and how much.

Impact

One

Available workarounds?

No and the platform is unusable

If the above answer is "Yes...", outline the workaround.

No response

Platform (Simple and/or Atomic)

No response

Logs or notes

No response

@dsas dsas added [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged labels Nov 7, 2024
@github-actions github-actions bot added [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts [Pri] High Address as soon as possible after BLOCKER issues labels Nov 7, 2024
@Robertght Robertght moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Nov 8, 2024
@Robertght
Copy link

📌 REPRODUCTION RESULTS

  • Tested on the platform - replicated

📌 ACTIONS

  • Triaged

📌 Message to Author
@dsas, is this a bug because we should have it by design, or can we consider it as an improvement/enhancement request?

@Robertght Robertght added Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Nov 8, 2024
@dsas
Copy link
Contributor Author

dsas commented Nov 8, 2024

It's arguable, I don't mind how it's termed. Previously there was an additional banner which said something like "upgrade to the premium plan to get access to lots of premium themes". It was removed because it was a duplicative CTA and that was confusing, but perhaps more should have been done to ensure the same details were still being shared.

@dsas dsas added the [Status] Needs Design Add this to PRs that need input from Design label Nov 21, 2024
@dsas dsas moved this from Triaged to Needs design in Automattic Prioritization: The One Board ™ Nov 21, 2024
@matticbot matticbot moved this from Needs design to Triaged in Automattic Prioritization: The One Board ™ Nov 21, 2024
@dsas
Copy link
Contributor Author

dsas commented Nov 21, 2024

@fditrapani this relates to your recent work on the theme details, just wondering if there's a simple change we can make here to resolve this quickly before any bigger changes come down the line.

@dsas dsas changed the title LITS: The theme grid is clearly marks required upgrades but theme details doesn't LITS: The theme grid clearly marks required upgrades but theme details doesn't Nov 21, 2024
@fditrapani
Copy link
Contributor

Thanks for the ping @dsas. I have been looking at this since we'd also like to get rid of the tooltips. I'm going to p2 the solution to get other folks to chime in but here's what I'm thinking. Starting with the showcase/design picker, we've been discussing removing the style variants and promoting free themes. I'd like to add a Free badge and update Upgrade > Paid since people in onboarding don't have a notion of our plans yet:

Image

Then on the Theme details screen, we'd reinforce the Free + Paid badges with the following:

Image

Image

Image

We can also consider swapping in the plan name for the showcase because at that point, I would hope people have been exposed to the plans and would have an idea what those names mean.

Let me know what you think here but like I said, I'd like to get this up on P2 for some better visibility as well.

@dsas
Copy link
Contributor Author

dsas commented Nov 21, 2024

I like those in general 👍

I'm unsure if just saying "Paid" on the grid, and just staying "Requires paid plan" on the theme details is descriptive enough. If a user is willing to pay for e.g. the personal plan and they keep stumbling across themes that are gated to the premium plan and it's many clicks to find that out, it could be annoying.

(The current design doesn't have this problem - it tells you the plan, but it doesn't tell you how much it costs).

@fditrapani
Copy link
Contributor

If a user is willing to pay for e.g. the personal plan and they keep stumbling across themes that are gated to the premium plan and it's many clicks to find that out, it could be annoying.

That's a good point. Thanks for bringing it up. I'll see if I can address it before posting something. Stay tuned.

@rcrdortiz
Copy link
Contributor

Moving this issue to our sprint backlog for visibility.

@rcrdortiz rcrdortiz added the Good First Issue Small, contained issues. label Nov 22, 2024
@fditrapani
Copy link
Contributor

I just shared an updated approach here on p2 that can be used for this: p9Jlb4-f80-p2

@fditrapani
Copy link
Contributor

fditrapani commented Dec 9, 2024

@rcrdortiz I documented the approach for the theme details page here: #95471 (comment)

to keep things simple, we could implement the updates to the theme details page separately.

@oskosk oskosk added [Pri] Normal Schedule for the next available opportuinity. and removed [Pri] High Address as soon as possible after BLOCKER issues labels Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good First Issue Small, contained issues. [Pri] Normal Schedule for the next available opportuinity. [Status] Escalated to Product Ambassadors [Status] Needs Design Add this to PRs that need input from Design [Status] Priority Review Triggered Quality squad has been notified of this issue in #dotcom-triage-alerts Triaged To be used when issues have been triaged. [Type] Bug When a feature is broken and / or not performing as intended
Projects
Development

Successfully merging a pull request may close this issue.

6 participants