Skip to content

AI Transport docs: sort Features nav section alphabetically#3468

Draft
VeskeR wants to merge 1 commit into
mainfrom
docs-ait-nav-sort
Draft

AI Transport docs: sort Features nav section alphabetically#3468
VeskeR wants to merge 1 commit into
mainfrom
docs-ait-nav-sort

Conversation

@VeskeR

@VeskeR VeskeR commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Summary

The AI Transport Features navigation section had grown to 18 entries in an ad-hoc order, which made the sidebar hard to scan and made it difficult to locate a specific feature. This PR sorts that list alphabetically by display name so the section has a predictable, scannable order.

Scope

Only the Features list in src/data/nav/aitransport.ts is reordered. Sections whose order carries meaning are intentionally left unchanged:

  • Getting started and Frameworks follow the intended SDK progression (Core SDK → Vercel AI SDK → Vercel WDK → Temporal).
  • Concepts follows the object-model / learning progression (Sessions → Connections → Runs → Steps → Invocations → …), so alphabetizing would scatter the model hierarchy.
  • Production, API reference, and Internals are short and already grouped logically (for example, API reference keeps the Core → Vercel → Temporal SDK grouping).

No pages are added, removed, or relinked — the diff is a pure reordering (34 insertions / 34 deletions) and all 18 feature links are intact.

New Features order

Agent presence · Branching, edit, and regenerate · Cancellation · Chain of thought · Concurrent turns · Database hydration · Double texting · Durable execution · History and replay · Human-in-the-loop · Interruption · LiveObjects State · Multi-device sessions · Optimistic updates · Push notifications · Reconnection and recovery · Token streaming · Tool calling

Notes

  • Based on main (not the in-flight WDK docs branch) so it is a clean, standalone change. The WDK nav entries live in Getting started and Frameworks, which are untouched here, so there is no overlap.
  • Opened as a draft to confirm the ordering decision and scope before finalizing. If you also want the API reference method lists or the Internals section alphabetized, that is a quick follow-up.

🤖 Generated with Claude Code

The Features section had grown to 18 entries in an ad-hoc order, which
made the sidebar hard to scan and made it difficult to locate a specific
feature. Sorting the list alphabetically by display name gives the
section a predictable, scannable order.

Scope is deliberately limited to the Features list. Sections whose order
carries meaning are left unchanged: Getting started and Frameworks follow
the intended SDK progression (Core SDK, Vercel AI SDK, Vercel WDK,
Temporal), and Concepts follows the object-model hierarchy (sessions,
connections, runs, steps, invocations). No pages are added, removed, or
relinked; the change is a pure reordering.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

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.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: ac543bbc-5fd0-48f2-9c5c-f1c788f9b59a

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
  • Commit unit tests in branch docs-ait-nav-sort

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.

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.

2 participants