Skip to content

docs: rename CLI to Node CLI, move Go CLI next to it#19

Merged
Krishan27 merged 1 commit into
mainfrom
docs/sidebar-node-go-parity
Jul 6, 2026
Merged

docs: rename CLI to Node CLI, move Go CLI next to it#19
Krishan27 merged 1 commit into
mainfrom
docs/sidebar-node-go-parity

Conversation

@flaglint

@flaglint flaglint commented Jul 6, 2026

Copy link
Copy Markdown
Owner

Summary

  • Renamed the "CLI" sidebar group to "Node CLI" — it implicitly meant "the JS one" while "Go CLI" was explicitly labeled, an asymmetry that got confusing once there were two languages.
  • Moved "Go CLI" from after Integrations (behind 6 JS-specific groups) to right after "Start Here", so both language tracks sit adjacent.
  • Left Concepts/Tutorials/Guides/Reference/Integrations generic/unlabeled — Go's docs are intentionally more compact right now (one bundled group matching its current 3-command scope), not because it needs parallel "Node Tutorials"/"Node Guides" groups yet.

Test plan

  • npm run build — clean, no duplicate-slug errors, 90 pages
  • Verified in-browser: sidebar order is Start Here → Go CLI → Node CLI → Concepts → ... → Trust → Blog

The bare "CLI" label implicitly meant "the JS one" while "Go CLI" was
explicitly labeled — an asymmetry that made the unlabeled group ambiguous
now that there are two languages. Renamed to "Node CLI" for parity.

Also moved the "Go CLI" group from after Integrations (buried behind 6
JS-specific groups) to right after "Start Here", so the two language
tracks sit adjacent instead of a Go visitor having to scroll past
Concepts/Tutorials/Guides/Reference/Integrations to find it.

Left Concepts/Tutorials/Guides/Reference/Integrations unlabeled/generic —
they're still JS-only in practice, but Go's docs are intentionally more
compact right now (one bundled "Go CLI" group matching its current
3-command scope), not because it needs parallel "Node Tutorials"/"Node
Guides" groups yet. Forcing full symmetry there would overstate how much
Go documentation actually exists today.

Signed-off-by: Krishan Kant Sharma <krishansharma0327@gmail.com>
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@flaglint, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0a553086-b800-4519-b6e0-a750ad8aeb57

📥 Commits

Reviewing files that changed from the base of the PR and between 587e1e8 and 0367429.

📒 Files selected for processing (1)
  • astro.config.mjs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/sidebar-node-go-parity

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.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying flaglint with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0367429
Status: ✅  Deploy successful!
Preview URL: https://dc784b65.flaglint.pages.dev
Branch Preview URL: https://docs-sidebar-node-go-parity.flaglint.pages.dev

View logs

@Krishan27 Krishan27 merged commit fc2cbfc into main Jul 6, 2026
4 checks passed
@Krishan27 Krishan27 deleted the docs/sidebar-node-go-parity branch July 6, 2026 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants