[EDU-2094] - Update Chat docs landing page to improve the reasons to use #2863
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
This is a great start. I think we could go a little futher in this too, though.
The 'features' section needs some love IMO - should we try utilising the tile component here?
I think we should also shout about the use case guide (admittedly it's only 1 at the moment, but still).
I also wonder if we sort this properly then the next steps become a bit redundant if this is a true landing page.
| * [Getting started: Chat in Android](/docs/chat/getting-started/android) | ||
| * [Getting started: Chat in Kotlin (JVM)](/docs/chat/getting-started/jvm) | ||
| * [Getting started: Chat in Swift](/docs/chat/getting-started/swift) | ||
| ## Why Chat |
There was a problem hiding this comment.
Can we make this 'Why Ably Chat'?
I think we should then have some content under this heading that covers the fact that Chat is built upon Pub/Sub and also the platform (need a good way to word both of these ideally).
We then have some redundancy with the final sentence in the previous paragraph.
| * [Getting started: Chat in Swift](/docs/chat/getting-started/swift) | ||
| ## Why Chat | ||
|
|
||
| ### Built for Serious Scale & Reliability |
There was a problem hiding this comment.
Sentence case and no ampersands please 🙂
|
|
||
| ### Built for Serious Scale & Reliability | ||
|
|
||
| Ably Chat is powered by Ably's globally distributed platform that handles **550 billion messages per month** and **1 billion+ connections per month**, serving the world's most demanding workloads with **100% uptime over 5+ years**. With a global edge network featuring **635 points of presence**, Ably Chat delivers messages with **<50ms median roundtrip latency** and provides automatic multi-region failover to ensure your chat experiences are always available. |
There was a problem hiding this comment.
Might be worth splitting the scale part and reliability part into separate paragraphs here, otherwise you get a a lot of 'withs' together, and a lot of bold text. Might also need some revision with an updated section above that covers it being built on the platform.
We should also link out to the platform section, or architectural section when discussing these numbers.
Should '550 billion' have a + ?
|
|
||
| ### Cost-Effective Scalability | ||
|
|
||
| Scale without penalty using Ably's usage-based pricing model that charges by-the-minute for what you actually use. The platform includes built-in cost optimization features like **message batching** to reduce consumption, and **volume discounts** that lower your overall cost as you grow. This means you can power more chat functionality within budget without stifling innovation for fear of cost. |
There was a problem hiding this comment.
This is only covering usage-based pricing and ignores MAU.
|
|
||
| Get building with intuitive APIs and comprehensive SDKs across multiple platforms. The Chat SDK abstracts away architectural complexity, enabling your team to rapidly ship exceptional chat experiences. Pre-built **React UI Kits** and **React Hooks** accelerate development even further, letting you focus on creating unique experiences rather than building chat infrastructure from scratch. | ||
|
|
||
| ### Enterprise-Ready |
There was a problem hiding this comment.
I think I'd swap this around with the 'develop productivity' as that leads into the getting started guides.
|
|
||
| ### Developer Productivity | ||
|
|
||
| Get building with intuitive APIs and comprehensive SDKs across multiple platforms. The Chat SDK abstracts away architectural complexity, enabling your team to rapidly ship exceptional chat experiences. Pre-built **React UI Kits** and **React Hooks** accelerate development even further, letting you focus on creating unique experiences rather than building chat infrastructure from scratch. |
There was a problem hiding this comment.
I think this needs a little thinking on how it flows into the getting started guides (should it be combined?) and the 'features' section further down.
I'm not sure hooks warrant being called out as that's expected in a React package I think.
Might also be worht pulling out UI kits separately - or look whether that should be part of the 'features'?
| ## Get started now <a id="get-started"/> | ||
|
|
||
| <Tiles> |
There was a problem hiding this comment.
Need some sort of run on, or intro text about SDK availability (similar to what you covered in the dev productivity section.
We should likely still pull UI kits out separately too IMO.
|
I also think we should pull in some imagery - whether that's architectural, or indicative of what you can build. |
Description
(Please ignore the big space between tiles and the rest. This has been addressed in my other PR (#2830) , which I expect to merge in the next day or two)
Updated the Chat landing page to better align with the product page marketing, addressing
feedback that the documentation was lacking in selling points, statistics, and facts about
Ably Chat's capabilities.
Changes
100% uptime over 5+ years, 635 POPs, <50ms latency)
discounts
premium support
icons and descriptions for better UX
Impact
This brings the documentation landing page more in line with the marketing messaging on
ably.com/chat, helping developers understand not just how to use Ably Chat, but why they
should choose it for their chat infrastructure needs. The visual tiles make it easier for
developers to quickly find and access the SDK guide for their preferred platform.