docs: rewrite Overview section and add landing page#1190
Merged
Conversation
3b080c9 to
36f02cc
Compare
Contributor
Author
|
related RFE to update the diagram: #1192 (not critical path) |
Collaborator
ajf
approved these changes
Apr 28, 2026
Collaborator
ajf
left a comment
There was a problem hiding this comment.
lgtm after commits get signed
ebe55b5 to
010dd0d
Compare
Contributor
Author
|
commits are signed now |
Merged
6 tasks
010dd0d to
b7211b7
Compare
1230446 to
284c8bf
Compare
|
🌿 Preview your docs: https://nvidia-preview-pull-request-1190.docs.buildwithfern.com/infra-controller |
8 tasks
Contributor
|
284c8bf to
7789860
Compare
Rewrites the entire Overview section of the NICo documentation and adds a new landing page, following the IA recommendation from CDEVS-2173. Overview section (5 pages): - What is NICo? — intro, "Why NICo exists" (sourced from VDR/Code Yellow), architecture overview with NICo Components and Prerequisite Components matching the architecture diagram, "Where NICo fits" stack diagram - Key Capabilities — hardware readiness, DPU lifecycle, multi-tenancy, trust/attestation, firmware control, deployment flexibility, GB200 rack-scale - Operational Principles — 5 foundational design principles - Day 0/1/2 Lifecycle — three operational phases - Scope and Boundaries — two-column tables showing NICo vs platform responsibilities (renamed from "What NICo Does Not Cover") Landing page (index.md): - Persona-based entry points: Deploy & Operate, Integrate, Evaluate - Quick links to HCL, release notes, FAQs, GitHub repos Other changes: - Replace "NCX Infra Controller" with "NVIDIA Infra Controller" in prose - Replace "GB200/GB300-class AI infrastructure" with "AI factory-scale infrastructure" - Fix /admin UI protocol: HTTP → HTTPS - Fix database name: forgedb → forge_system_carbide - Remove Route Server from NICo Components (not a NICo-deployed service) - Remove hand-wavey/marketing language across all overview pages - Remove duplicative content between overview pages - Add explicit URL slugs to prevent Fern slug mangling (what-is-ni-co) - Replace stale Introduction page (README.md) with new landing page Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Andrew Liu <andreliu@nvidia.com>
7789860 to
4d019dc
Compare
Contributor
Author
|
@benhuntley issues addressed across both #1190 and #1227 |
Contributor
Author
|
/ok to test 4d019dc |
Contributor
Author
|
@Coco-Ben please review |
Coco-Ben
approved these changes
May 5, 2026
Coco-Ben
added a commit
that referenced
this pull request
May 6, 2026
…d reference installation (#1227) ## Summary Adds the Getting Started section to the NICo documentation, covering the full deployment path from prerequisites through first host discovery. - **Prerequisites** (4 pages): Hardware, Network, Software, BMC/OOB — consolidated from site-reference-arch.md, site-setup.md, and networking_requirements.md - **Building NICo Containers**: repositioned in nav before Quick Start - **Quick Start Guide**: 7-step deployment walkthrough (build → K8s → configure → deploy → verify → OOB → first host) with site configuration pulled from helm-prereqs/README.md - **Reference Installation**: manual phase-by-phase installation from SETUP_PHASES.md, plus PKI architecture, PostgreSQL architecture, and troubleshooting - **Provisioning (Day 0 Operations)**: new section with Ingesting Hosts, Host Validation, SKU Validation - **helm-prereqs/README.md**: slimmed to lightweight pointer to docs site - Old pages removed where fully superseded (site-reference-arch, site-setup, networking_requirements, expected_machine_update, bootstrap) - TLS/SPIFFE page moved from kubernetes/ to development/ - CLI naming standardized: admin-cli (gRPC) vs carbide-cli (REST) with distinction table ## Context Part of NICo Docs Code Yellow (FORGE-8168). Follows the IA recommendation from CDEVS-2173 for the Getting Started section structure. Builds on the Overview section work in PR #1190. ## Test plan - [ ] Preview with `fern docs dev` — verify all nav links resolve - [ ] Walk through Quick Start Guide steps 1-7 for completeness - [ ] Verify prerequisite pages cover all content from removed old pages - [ ] Verify Reference Installation troubleshooting section is complete - [ ] Check landing page persona table links resolve to new page paths - [ ] Verify helm-prereqs/README.md links point to published docs URLs 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: Peter Gambrill <pgambrill@nvidia.com> Signed-off-by: Andrew Liu <andreliu@nvidia.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Peter Gambrill <pgambrill@nvidia.com>
inf0rmatiker
pushed a commit
to inf0rmatiker/infra-controller
that referenced
this pull request
May 7, 2026
## Summary - **Landing page** (`docs/index.md`): persona-based entry points for operators, integrators, and evaluators — replaces the stale Introduction page - **Overview section** (5 pages): complete rewrite covering What is NICo, Key Capabilities, Operational Principles, Day 0/1/2 Lifecycle, and Scope and Boundaries - **What is NICo** (`what-is-nico.md`): architecture overview with NICo Components (green boxes) and Prerequisite Components (white boxes) matching the architecture diagram; "Why NICo exists" framing sourced from VDR and Code Yellow docs - **Scope and Boundaries** (renamed from "What NICo Does Not Cover"): two-column tables showing NICo vs platform/operator responsibilities at each boundary - **Nav fixes**: explicit slugs to prevent Fern from mangling NICo in URLs (e.g. `what-is-ni-co` → `what-is-nico`) ## Context Part of the NICo Docs Code Yellow (FORGE-8168). Follows the IA recommendation from CDEVS-2173 for the Overview section structure and landing page. ## Test plan - [ ] Preview with `fern docs dev` — verify all nav links resolve, no broken internal links - [ ] Verify Overview sidebar matches: Home → What is NICo? → Key Capabilities → Operational Principles → Day 0/1/2 Lifecycle → Scope and Boundaries - [ ] Verify landing page persona table links resolve to correct pages - [ ] Verify URL slugs use `what-is-nico` and `scope-and-boundaries` (not `what-is-ni-co`) - [ ] Review component descriptions in architecture overview against the architecture diagram 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: Andrew Liu <andreliu@nvidia.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
inf0rmatiker
pushed a commit
to inf0rmatiker/infra-controller
that referenced
this pull request
May 7, 2026
…d reference installation (NVIDIA#1227) ## Summary Adds the Getting Started section to the NICo documentation, covering the full deployment path from prerequisites through first host discovery. - **Prerequisites** (4 pages): Hardware, Network, Software, BMC/OOB — consolidated from site-reference-arch.md, site-setup.md, and networking_requirements.md - **Building NICo Containers**: repositioned in nav before Quick Start - **Quick Start Guide**: 7-step deployment walkthrough (build → K8s → configure → deploy → verify → OOB → first host) with site configuration pulled from helm-prereqs/README.md - **Reference Installation**: manual phase-by-phase installation from SETUP_PHASES.md, plus PKI architecture, PostgreSQL architecture, and troubleshooting - **Provisioning (Day 0 Operations)**: new section with Ingesting Hosts, Host Validation, SKU Validation - **helm-prereqs/README.md**: slimmed to lightweight pointer to docs site - Old pages removed where fully superseded (site-reference-arch, site-setup, networking_requirements, expected_machine_update, bootstrap) - TLS/SPIFFE page moved from kubernetes/ to development/ - CLI naming standardized: admin-cli (gRPC) vs carbide-cli (REST) with distinction table ## Context Part of NICo Docs Code Yellow (FORGE-8168). Follows the IA recommendation from CDEVS-2173 for the Getting Started section structure. Builds on the Overview section work in PR NVIDIA#1190. ## Test plan - [ ] Preview with `fern docs dev` — verify all nav links resolve - [ ] Walk through Quick Start Guide steps 1-7 for completeness - [ ] Verify prerequisite pages cover all content from removed old pages - [ ] Verify Reference Installation troubleshooting section is complete - [ ] Check landing page persona table links resolve to new page paths - [ ] Verify helm-prereqs/README.md links point to published docs URLs 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: Peter Gambrill <pgambrill@nvidia.com> Signed-off-by: Andrew Liu <andreliu@nvidia.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Peter Gambrill <pgambrill@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/index.md): persona-based entry points for operators, integrators, and evaluators — replaces the stale Introduction pagewhat-is-nico.md): architecture overview with NICo Components (green boxes) and Prerequisite Components (white boxes) matching the architecture diagram; "Why NICo exists" framing sourced from VDR and Code Yellow docswhat-is-ni-co→what-is-nico)Context
Part of the NICo Docs Code Yellow (FORGE-8168). Follows the IA recommendation from CDEVS-2173 for the Overview section structure and landing page.
Test plan
fern docs dev— verify all nav links resolve, no broken internal linkswhat-is-nicoandscope-and-boundaries(notwhat-is-ni-co)🤖 Generated with Claude Code