-
Notifications
You must be signed in to change notification settings - Fork 6
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
Change update message in onboarding of starter sites #330
Comments
cc @harshitarora-in if you have any input about the wording used or approach in general |
@vytisbulkevicius, why do you think is relevant to mention the Agency as well? FMHO it looks confusing having that. If the previous texts(before the new onboarding) were well received and statistically clearer, why we can't use them and we need to invent new terminologies. |
https://vertis.d.pr/hleFPd this is how is used to be. #143 (comment) |
@selul, I didn't think mentioning both packages would cause confusion as we provide more information (that both packages Business or Agency) are options to upgrade. Also, as we mention Business explicitly maybe it works psychologically that they are looking for exactly this package to upgrade and not considering Agency. I'm fine with having only Business mentioned but don't see confusion with mentioning both options. |
So, from your point of view, usually, when you pay a higher plan, you might get things removed vs the lower one? I have not yet encountered any situation where if I buy a higher plan, I don't get things available in the lower one, not sure if you have. My recommendation is based on past experience with the old messaging that we had and support feedback that those were clearer and less causing the confusion that we have now with naming which I thing is safest vs testing new messaging without any clear path of validating their success. |
No, that's not something I experienced with the plans, I was putting emphasis on the fact that mentioning both plans that gives what they need shouldn't hurt and only give more clarity but let's follow your recommendation and use the old way that was working (the benefit with it is to have a shorter text). (edited my suggestions in the issue description) Thanks for the help |
🎉 This issue has been resolved in version 1.2.8 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
As reported in this issue - https://github.com/Codeinwp/neve-pro-addon/issues/2729
There is a confusion created by the wording we use in the onboarding.
We have it here:
Or when we click on any PRO starter site and preview it:
We need to upgrade the wording from:
From:
To:
From:
To:
Also, as @selul suggested on https://github.com/Codeinwp/neve-pro-addon/issues/2729#issuecomment-1890976348
it would be great to make this:
Keep the same pages/tables but hide the first plan if they arrive on the page based on any upgrade links from the Starter Sites context.
The text was updated successfully, but these errors were encountered: