Repository navigation
docs: reformat ecosystem page to template shape - #1579
Conversation
Restructure the About > Ecosystem page around the NVIDIA docs ecosystem page template: positioning intro, a cross-reference Tip, a 'NeMo Gym Within NVIDIA NeMo' section with sibling libraries and Gym's role, a 'Choosing Between NeMo Gym and NeMo Evaluator' comparison, and a renamed 'Related Products' reference section. All existing integration content (Environment Libraries, Training Framework Libraries, Agent Harnesses, related-library tables) is preserved. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Lawrence Lane <llane@nvidia.com>
|
🌿 Preview your docs: https://nvidia-preview-lbliii-ecosystem-doc-template.docs.buildwithfern.com/nemo/gym Here are the markdown pages you've updated: |
sephmard
left a comment
sephmard
left a comment
There was a problem hiding this comment.
Accurate — no changes needed:
- Intro paragraph: "pairing a dataset, agent harness, and verifier so the same environment can drive both evaluation and training" — technically correct. A Gym environment is a resources server (dataset + verifier) paired with an agent harness.
- "NeMo Gym's role" paragraph: Accurate. Standardizing the agent harness, verifier, and session isolation is exactly what Gym does.
- cross-links: All three resolve — /about, /about#what-nemo-gym-provides (heading confirmed), /about/architecture.
- NeMo RL description: "Runs scalable post-training (GRPO, DPO, and SFT)" — correct.
- NeMo Curator description: "Prepares, filters, and deduplicates training data at scale" — correct.
Needs changes — Evaluator mentions to remove:
There are three places, not just the table:
- Intro paragraph — "While NeMo RL handles post-training and NeMo Evaluator runs benchmark evaluations..." — the Evaluator mention needs to come out here too.
- "NeMo Gym Within NVIDIA NeMo" bullet list — the NeMo Evaluator bullet needs to be removed.
- Comparison table — remove the entire section.
The Related Products table at the bottom already lists NeMo Evaluator as a plain row, which is fine — that's just a reference list, not a positioning claim.
One minor flag worth a comment:
The "NeMo Gym Within NVIDIA NeMo" section lists libraries in a pipeline order (Curator → Gym → NeMo RL → Evaluator). Once Evaluator is removed, the ordering still makes sense (Curator → Gym → NeMo RL) and doesn't need further changes.
| - **NeMo Curator**: Prepares, filters, and deduplicates training data at scale. | ||
| - **NeMo Gym**: Defines the environments — dataset, agent harness, and verifier — that agents are evaluated and trained in *(this library)*. | ||
| - **NeMo RL**: Runs scalable post-training (GRPO, DPO, and SFT) against those environments. | ||
| - **NeMo Evaluator**: Benchmarks model quality across standard evaluations. |
There was a problem hiding this comment.
Delete. Recommend removing this mention, as it is confusing. We are consolidating the Evaluator functionality directly into Gym.
|
|
||
| Readers often compare these libraries because both touch evaluation, but they solve nearby problems at different layers. | ||
|
|
||
| | Aspect | NeMo Gym | NeMo Evaluator | |
There was a problem hiding this comment.
Delete mention of Evaluator. Recommend removing this mention, as it is confusing. We are consolidating the Evaluator functionality directly into Gym.
|
|
||
| **NeMo Gym's role**: NeMo Gym is where a task becomes an interactive environment. It standardizes how an agent interacts with the world (the agent harness), how task completion is scored (the verifier), and how per-task state is isolated — producing the rollouts and reward signals that training frameworks like NeMo RL consume, and the consistent scoring that evaluation depends on. | ||
|
|
||
| ## Choosing Between NeMo Gym and NeMo Evaluator |
There was a problem hiding this comment.
We should remove this whole section - we want to ensure its clear that Gym is available for first-class evaluation workflows
Signed-off-by: Lawrence Lane <llane@nvidia.com>
| ## Related Products in the NVIDIA NeMo Ecosystem | ||
|
|
||
| Depending on your workflow, you may also find these libraries useful: | ||
| Depending on your workflow, you may also find these NeMo libraries useful across data preparation, evaluation and training, and deployment. |
There was a problem hiding this comment.
We removed Evaluator in favor of positioning Gym. But we still mention evaluation can be found in other NeMo libraries. Consider removing.
sephmard
left a comment
sephmard
left a comment
There was a problem hiding this comment.
One suggested change in comments. But approving as it otherwise looks good.
What
Reformats the About → Ecosystem page (
fern/versions/latest/pages/about/ecosystem.mdx) around the NVIDIA docs ecosystem page template shape.Note
This is an initial pass at standardizing around the ecosystem page template's recommended shape. The structure is in place — we can still massage the actual content/wording if desired.
Template elements applied
<Tip>cross-reference — links to the Overview, "What NeMo Gym Provides", and Architecture pages (all targets verified to resolve).## NeMo Gym Within NVIDIA NeMo— describes the platform, lists sibling libraries, and states NeMo Gym's role.## Choosing Between NeMo Gym and NeMo Evaluator— comparison table for the two most-confused libraries (contrasts focus only; no negative claims).## Related Products in the NVIDIA NeMo Ecosystem— renamed from "Related NeMo Libraries"; existing Data / Evaluation & Training / Deployment tables preserved.@tpl:comments, format-selection accordion).Preserved
All existing integration content is kept verbatim: Environment Libraries, Training Framework Libraries, Agent Harnesses, the contribution invite, and the related-library tables.
Fern adaptations
# H1— the About pages derive the H1/nav label from frontmattertitle:(title-source: frontmatter), so the template's literal H1 lives intitle:/intro instead. Kepttitle: "Ecosystem"to preserve the nav label and/about/ecosystemURL.latest/only — frozen GA snapshots (v0.3.0/,v0.2.1/) untouched per docs policy.Validation
fern check→ All checks passed🤖 Generated with Claude Code