Skip to content

docs: add AI Transport cross-references to key pages#3221

Open
mattheworiordan wants to merge 1 commit intomainfrom
feat/add-ai-transport-mentions
Open

docs: add AI Transport cross-references to key pages#3221
mattheworiordan wants to merge 1 commit intomainfrom
feat/add-ai-transport-mentions

Conversation

@mattheworiordan
Copy link
Member

@mattheworiordan mattheworiordan commented Feb 22, 2026

AI Transport is Ably's strategic priority but was missing from several high-visibility page. The About Ably page lists every product except it, the Building with LLMs page (literally about AI) doesn't mention it, and the llms.txt preamble omits it entirely. This PR adds light cross-references where there's a clear use case.

Changes

  • About Ably (platform/index.mdx): Added AI Transport product section after LiveSync, following the established pattern of the other product entries
  • Building with LLMs (ai-llms/index.mdx): Added an Aside note pointing to AI Transport, plus added AI Transport to both the product priority list and interface list in the LLM configuration prompt
  • llms.txt preamble (llmstxt.ts): Added "AI Transport" to the products list
  • llms.txt docs (llms-txt.mdx): Added AI Transport category description alongside the other products
  • Connection recovery (connection-recovery.mdx): Added a paragraph linking connection recovery to AI Transport's resumable token streaming — this is the exact mechanism AI Transport builds on, so it's a natural fit
  • Channels (channels/index.mdx): Added a further-reading aside at the bottom of the page

Placement trade-offs

Building with LLMs page - added an aside as the page is about using LLM coding assistants to build with Ably docs, not about AI Transport itself, but obviously could end up being a target for AI devs who click that form docs home page.

Channels page - added a further-reading aside. The intro explains channel concepts and jumping straight to "btw, AI Transport" felt premature. At the end, the reader has full context on what channels are and the cross-reference reads as "you might also want to know" rather than an interruption.

AI Transport was missing from several high-visibility pages including
the About Ably page, the Building with LLMs page, the llms.txt
preamble, and the channels concept page. This adds light cross-
references where there's a clear use case without polluting unrelated
Pub/Sub documentation.
@coderabbitai
Copy link

coderabbitai bot commented Feb 22, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/add-ai-transport-mentions

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sacOO7
Copy link
Contributor

sacOO7 commented Feb 23, 2026

Somewhat related: a Markdown variant of our documentation pages, optimized for LLM consumption, now includes related topics within the navigation footer → #3208

@rainbowFi
Copy link
Contributor

The update on the Channels page feels a little bit shoe-horned in, but I don't hate it. The other changes all look good.

Comment on lines +234 to +236
<Aside data-type='further-reading'>
If you are building AI-powered applications that stream LLM responses to users, [AI Transport](/docs/ai-transport) provides purpose-built features for token streaming, session management, and human-in-the-loop workflows on top of Ably channels.
</Aside>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does look a bit odd on this page, especially as it makes it look like it's related to channel groups when rendered. Can we drop it for now and get the rest in?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really think it's pretty common that users will want to stream tokens over channels, and we should capture the opportunity to direct them. Where do you think there's a better place to share this info?

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

Labels

review-app Create a Heroku review app

Development

Successfully merging this pull request may close these issues.

5 participants