docs: Consolidate DD library docs links

[mikeknep]

Summary by CodeRabbit

• Documentation
  • Updated Data Designer documentation links to use internal library documentation paths.
  • Added redirects for Data Designer library pages to the corresponding NVIDIA documentation.
  • Removed a duplicate external “Library Documentation” link from the Next Steps section.

[github-actions]

🌿 Preview your docs: https://nvidia-preview-dd-docs-constant-mknepper.docs.buildwithfern.com/nemo-platform

[coderabbitai]

📝 Walkthrough

Walkthrough

Data Designer overview, migration, and tutorial pages now use internal /data-designer-library/... links. A wildcard redirect maps those routes to the corresponding NVIDIA documentation URLs, and the duplicate Library Documentation card was removed.

Changes

Data Designer documentation links

Layer / File(s)	Summary
Library route redirect docs/fern/docs.yml	Adds a wildcard redirect from /data-designer-library/:slug* to the corresponding NVIDIA Data Designer documentation path.
Documentation link migration docs/data-designer/index.mdx, docs/data-designer/migration.mdx, docs/data-designer/tutorials/*	Replaces versioned external documentation URLs with internal library routes and removes the Library Documentation card.

Possibly related PRs

• NVIDIA-NeMo/nemo-platform#659: Updates overlapping Data Designer documentation links to another library documentation version.

Suggested reviewers: lbliii

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title matches the main change: consolidating Data Designer library documentation links.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dd-docs-constant/mknepper

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Suite	Lines Covered	Line Rate	Branch Rate
Unit Tests	24401/31577	77.3%	62.0%
Integration Tests	14023/30226	46.4%	19.3%

[mikeknep]

This card component is the only link to upstream DD docs that isn't a standard Markdown link, and it isn't especially valuable as a card here anyways, so I'm just deleting it.

[mikeknep]

Currently, the DD library only publishes the latest version of the docs with no version component at all, so we can't actually explicitly target a specific version when that version is the latest. This is getting fixed in the upstream library

[mikeknep]

This redirect approach seems the best option for consolidating the upstream DD library links:

• it achieves the goal of specifying the library version just once, here
• it allows authors to write normal-looking Markdown links (don't have to use a custom <DataDesignerDocsLink> component
• it's short

There is one unfortunate side-effect: fern's broken-links check doesn't understand redirects, and so all the DD links are flagged as broken 😒 These are currently only warnings, not errors, but still: not great. My agent suggested wrapping the broken-links check in a script that ignores the data-designer-library references. I'm tempted to punt that until we start actually blocking in CI on broken links (there is an existing one on main related to auth).

I also considered a pattern in which authors provide full-but-unversioned links in the markdown, and we use redirects to target the specific version. So for example the author would write [custom columns](https://docs.nvidia.com/nemo/datadesigner/custom-columns) and the redirect config would add in the version. Unfortunately, this does not work: you can't redirect from external sources, only from internal references (e.g. /foo); this also produced a slew of TypeErrors in Fern, including for completely unrelated links in the docs.

[mikeknep]

The other weird thing about this approach is that if you right-click the link and select "Copy link address", you get the invalid, pre-redirected link. Example from the preview build:

https://nvidia-preview-dd-docs-constant-mknepper.docs.buildwithfern.com/nemo-platform/data-designer-library/getting-started/welcome

If you paste that into a browser and try to hit it, it does correctly redirect, but it's still a little weird...

[mckornfield]

wow this is annoying lol. I guess it's valid technically as a link, just not to the final destination

[mckornfield]

I honestly don't know if this is an improvement with how weird it is. I will stamp it though if you feel it is hahaha

[mikeknep]

Chatted in Slack and we don't like any of the options enough. In particular, the /data-designer-library/* approach looks too much like an absolute link and/or a link that should exist in the repo's docs, and therefore is more confusing than it is valuable. We'll just keep relying on grep/fastmod/agents to update all the docs links as we update lib dep versions.