Skip to content

docs(extraction): add YAML frontmatter to remaining published pages#2332

Draft
kheiss-uwzoo wants to merge 1 commit into
NVIDIA:mainfrom
kheiss-uwzoo:docs/frontmatter-rollout
Draft

docs(extraction): add YAML frontmatter to remaining published pages#2332
kheiss-uwzoo wants to merge 1 commit into
NVIDIA:mainfrom
kheiss-uwzoo:docs/frontmatter-rollout

Conversation

@kheiss-uwzoo

Copy link
Copy Markdown
Collaborator

Summary

Adds YAML frontmatter to the remaining published extraction pages per the content IA audit (Chapter 4 — Metadata & Frontmatter). This is PR3 in the audit-driven docs series, following #2330 (orphans) and #2331 (naming).

Coordinates with #2291: Phase 1 IA already adds frontmatter to six entry-path pages (overview, getting-started-about, deployment-options, workflow-document-ingestion, multimodal-extraction, plus external-documentation-map and retriever-cli-quickstart). This PR covers the other 17 nav-published pages so the full extraction corpus has metadata once both land.

Changes

Adds a YAML frontmatter block to each file (no body prose or nav changes):

  • concepts.md, releasenotes.md, prerequisites-support-matrix.md, api-keys.md
  • audio-video.md, embedding.md, vdbs.md, ray-logging.md
  • customize-extend.md, starter-kits.md, evaluate-on-your-data.md
  • nemo-retriever-api-reference.md, environment-config.md, content-metadata.md
  • troubleshoot.md, faq.md, contributing.md

Schema matches #2291 (content_type, audience, journey_stage, product, features, technologies, prerequisites, optional duration_minutes, surface, status).

Scope / safety

  • Docs-only. No mkdocs.yml, runtime code, or link-target changes.
  • Strict build passes: mkdocs build --strict.
  • Frontmatter is additive metadata for findability, agent readability, and Fern migration prep.

Merge note

If #2291 lands first, this PR should rebase cleanly (disjoint file set). If both are open, merge #2291 before #2332 to avoid duplicate frontmatter work on the six overlap pages (there is none by design).

Test plan

Roll out machine-readable metadata (Chapter 4, content IA audit) to the
17 published extraction pages not already covered by NVIDIA#2291. Uses the same
frontmatter schema as Phase 1 IA prep: title, content_type, audience,
journey_stage, product, features, technologies, prerequisites,
duration_minutes (where applicable), surface, and status.

Prose and navigation unchanged. Strict mkdocs build passes.
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