Skip to content

docs: restructure About Building Workflows to the about-procedural-task template#2058

Draft
chenopis wants to merge 1 commit into
NVIDIA:developfrom
chenopis:docs/about-building-workflows-template-conformance
Draft

docs: restructure About Building Workflows to the about-procedural-task template#2058
chenopis wants to merge 1 commit into
NVIDIA:developfrom
chenopis:docs/about-building-workflows-template-conformance

Conversation

@chenopis

Copy link
Copy Markdown

What

Restructures About Building NVIDIA NeMo Agent Toolkit Workflows (docs/source/build-workflows/about-building-workflows.md) to conform to the about-procedural-task documentation template.

Why

This page is the cited example for the "Introductory About Procedural Task Topic" template in NVIDIA's tech-docs template-library, but its section structure had diverged from that template. This change (from a template-library conformance audit) realigns it.

Change

  • Reorganizes the existing content under the template's prescribed H2 sections: Workflow Overview, Key Concepts, Common Approaches, Decision Factors.
  • Adds a per-agent Best for note to the agents list under Common Approaches.
  • Adds a Router Agent vs Sequential Executor comparison table under Decision Factors.
  • Preserves all existing prose, links, the YAML config example, and the SPDX license header verbatim.
  • New descriptive text (the "Best for" notes and the comparison-table cells) is sourced from the corresponding agent doc pages, not invented.

Opened as draft — this is a proposed structural alignment to the docs template. Maintainers may prefer different "Best for" phrasing, or to keep the existing structure; happy to adjust.

🤖 Generated with Claude Code

…sk template

This page is the NVIDIA tech-docs template-library's cited example for
the "Introductory About Procedural Task Topic" template, but its heading
structure had diverged from that template. Reorganizes the existing
content under the template's prescribed H2 sections (Workflow Overview,
Key Concepts, Common Approaches, Decision Factors), adds a per-agent
"Best for" note to the agent list, and adds a Router-vs-Sequential
comparison table.

All existing prose, links, the YAML example, and the SPDX license header
are preserved verbatim. New descriptive text (the "Best for" notes and
the comparison-table cells) is sourced from the corresponding agent doc
pages, not invented.

Signed-off-by: Andrew Chen <andrewch@nvidia.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@copy-pr-bot

copy-pr-bot Bot commented Jun 11, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: beb10ea5-f9d5-4b97-bf11-9c0ef10702a8

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

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

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.

1 participant