docs: group nodes into Core, Partner, and Custom Nodes - #1330
docs: group nodes into Core, Partner, and Custom Nodes#1330robinjhuang wants to merge 2 commits into
Conversation
Rename the Built-in Nodes tab to Nodes and give it three groups: Core Nodes (the built-in reference), Partner Nodes (moved from Get Started), and Custom Nodes (install, develop, and registry docs moved from Get Started and Development). The Registry API Reference tab becomes a group under Registry. Add an overview page for the tab comparing the three kinds of nodes, and one for the Custom Nodes group. Teach the i18n nav sync to keep groups that render an OpenAPI spec instead of pages, so the nested Registry API reference survives a sync and keeps its localized title. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 5 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Comment |
🌐 i18n translation sync reminder@comfyui-wiki English documentation was updated in this PR. Please complete or schedule translation updates for the following files: Japanese (
|
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
1 participant
Summary
Renames the Built-in Nodes tab to Nodes and organizes it into three groups: Core Nodes (the built-in node reference), Partner Nodes (moved from Get Started), and Custom Nodes (install, develop, and registry docs moved from Get Started and Development). The Registry API Reference tab is now a group nested under Registry.
Adds two overview pages:
/nodesexplains what a node is and how core, partner, and custom nodes differ, and/custom-nodesintroduces the Custom Nodes group.The i18n nav sync now keeps groups that render an OpenAPI spec instead of pages, so the nested Registry API reference survives a sync and keeps its localized title. zh/ja/ko navigation mirrors the new structure; the two new pages are English-only until the translation pipeline runs.