[AIT-1226] Merge the AI Transport About and Why pages into one landing page - #3505
Draft
VeskeR wants to merge 2 commits into
Draft
[AIT-1226] Merge the AI Transport About and Why pages into one landing page#3505VeskeR wants to merge 2 commits into
VeskeR wants to merge 2 commits into
Conversation
Two pages at the top of the AI Transport nav were doing overlapping jobs: "About AI Transport" introduced the product, and "Why AI Transport" argued for it. A reader arriving from marketing or from another product's docs had to read both to get either answer, and each page repeated the other's framing. Collapsing them puts the high-level content in one place and lets the "Why AI Transport?" section sit above "Getting started", where the question it answers actually gets asked. The merged page keeps /docs/ai-transport, because that is the URL 26 inbound references already use as the product entry point, and moving it would have put a redirect on the highest-traffic path into the section. The page is written to answer necessity rather than comprehension. Two founder calls in late July concluded that readers understood the product and still could not see why they needed it before a V2, and that the scale-oriented framing actively invited "nice to have". So the page opens on the failure modes a reader already has, states that the threshold is response duration rather than traffic volume, shows both seams that change when retrofitting an application that already streams, and names the constraints and dependencies adoption brings. Several claims carried by the old pages are gone because the roadmap, the feature pages, and the SDK do not support them: LangChain and native model-provider integrations, human handover, two platform statistics that appear nowhere else in the docs, and a publish-order guarantee that message-ordering.mdx explicitly refutes for cross-region publishers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
The tradeoffs table hung data portability off webhook and Kafka egress, which does not support it: those sources document channel.message, and nothing says the append operations that carry a streamed response are delivered outbound. Dropping the claim entirely was the wrong correction, because database hydration does support it by a different route: an agent that persists each completed run holds the conversation, since the union of completed runs reconstructs it losslessly. Gives that its own row sourced to database hydration, and leaves webhooks and Kafka scoped to the analytics and audit use they are documented for. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
VeskeR
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes AIT-1226.
Collapses
Getting started > About AI TransportandWhy AI Transport? > Overviewinto one page, and movesWhy AI Transport?aboveGetting started:The merged page stays at
/docs/ai-transportso the product entry point keeps its URL./docs/ai-transport/whyredirects to it and picks up the/docs/ai-transport/concepts/infrastructureredirect the deleted page carried.why/http-streaming-and-ai.mdxkeeps its URL.The page is rewritten rather than concatenated. It opens on the failure modes a reader already has, uses one comparison table as the central artifact with the feature links in it, adds a section on what adopting a session layer costs you, and shows both the agent-side and client-side code seams. Claims the old pages made that
roadmap.mdx, the feature pages, or the SDK typings do not support have been dropped.The other five files are link updates to match.
🤖 Generated with Claude Code