Pricing: mention custom domain limitations

[humitos]

We agreed on:

• 2 domains per project on community
• 5 domains per organization on Advanced
• 15 domains per organization on Pro

This is the first step: update our pricing page for new customer. One of the next steps involves enforcing this in our application by adding Read the Docs features to the plans and also showing the domains left in the admin.

Related https://github.com/readthedocs/readthedocs-corporate/issues/1808

---

📚 Documentation preview 📚: https://readthedocs-about--305.org.readthedocs.build/

[stsewd]

Do we have the number of projects using more than one domain on .org?

[humitos]

We have 102 projects with more than 2 domains.

In [2]: Project.objects.annotate(n_domains=Count("domains")).filter(n_domains__gt=2).count()
Out[2]: 102

First 15 projects with many domains:

In [15]: list(Project.objects.annotate(n_domains=Count("domains")).filter(n_domains__gt=2).order_by("-n_domains")[:15].values_list("slug", flat=True))
Out[15]: 
['www',
 'readthedocs',
 'gooddal',
 'thiet-ke-web',
 'trevorbramwellnet',
 'astro-thesis',
 'stdlib-examples',
 'ompi',
 'zfsbootmenu',
 'python3info',
 'workshop-devops',
 'pirateweather',
 'astronaut-training-program',
 'jquantlib',
 'docoftheyear']

[ericholscher]

Looks good to me. I do think we want to add the domain count somewhere in the dashboard, though I feel like we need an "Organization status" page or something, but probably start on the Domains page for the project?

[humitos]

I do think we want to add the domain count somewhere in the dashboard, though I feel like we need an "Organization status" page or something

Yes, we want to this. It's also gonna be useful for the other pricing change we've been talking about regarding build time limits 👍🏼

but probably start on the Domains page for the project?

I'm not sure if we want to expose the number of domains used by the whole organization to project admins. However, I think we should add a form validation that fails if they ran out of domains saying they should talk to the organization owner. Then, the organization owner is the one that can access the "organization status" page and check these numbers.

Thoughts?

[ericholscher]

I don't think it's a huge deal to expose the total number of domains, but I'm also fine just erroring on the validation as a starting point. We could even do something like "You have $x domains remaining" or similar, but I think it's also fine to just have a "Using 5/10 domains", it's not exposing any secrets.

[humitos]

I'm merging this PR, but I created another issue to track the changes on the domain/admin page to show the available ones and limit the creation if the limit is reached.