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

Change request for: /docs/pricing/standard #2465

Open
sgr2022 opened this issue Mar 5, 2025 · 0 comments
Open

Change request for: /docs/pricing/standard #2465

sgr2022 opened this issue Mar 5, 2025 · 0 comments

Comments

@sgr2022
Copy link

sgr2022 commented Mar 5, 2025

Page name: Standard
URL: /docs/pricing/standard

Requested change or enhancement:

I think that it would be useful and clearer for customers to show, under this page, both options:

1- How to upgrade from Free to Standard (which is not there yet)
2- How to upgrade from Stand to Pro (which is there now)

I realise that the instructions for upgrading from Free to Stand are covered under the https://ably.com/docs/pricing/free page section, but I think that intuitively as a customer I would be looking for it under Standard rather than under the Free package section. I personally found it confusing when I clicked on Standard (specifically looking for instructions on how to upgrade to that package) and found that I only had instructions on how to upgrade from Standard, even though we do cover downgrading from Stand to Free there.

IMO if customers are wondering about a certain package (Standard in this case) they won't click on the free package section in order to find out how to upgrade to Stand, but they will go to the Stand section itself.

The same would apply to the PRO section (I think that we should cover both scenarios there: upgrading from Stand to Pro and from Pro to whatever)

I think that this would flow a bit better in the way that I think people would naturally browse the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant