[WIP] docs: add Fern website developer guide for building and publishing docs#6299
[WIP] docs: add Fern website developer guide for building and publishing docs#6299Jont828 wants to merge 3 commits intoai-dynamo:mainfrom
Conversation
Explains the dual-branch architecture (main vs docs-website), the three CI jobs (lint, sync-dev, release-version), callout conversion, version management, and common maintenance tasks.
Add a "Developer Guide" section to the Fern sidebar navigation and move the Fern website documentation into it as a proper docs page at pages/development/fern-website.md. The page covers the dual-branch architecture, CI workflows, callout conversion, version management, publishing flow, and common maintenance tasks.
- Add a note clarifying the site is hosted on Fern and that docs.dynamo.nvidia.com is a custom domain alias pointing to it - Add a full "Running Locally" section covering: installing the Fern CLI, creating the fern/ symlink, fern check, fern docs broken-links, and fern docs dev for local preview - Remove the old "Preview docs locally" subsection that was a subset of this content - Update URL table to clarify primary vs alias relationship
|
👋 Hi Jont828! Thank you for contributing to ai-dynamo/dynamo. Just a reminder: The 🚀 |
WalkthroughAdds comprehensive documentation for the Fern-based Dynamo docs website, explaining architecture, workflows, configuration, version management, and publication procedures. Updates navigation configuration to expose the new documentation. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
||
| --- | ||
|
|
||
| ## GitHub Workflows |
There was a problem hiding this comment.
We should add a mention here that there's also a workflow in the docs-website branch that runs when you push directly to that branch
| Runs two independent link-checking jobs: | ||
|
|
||
| | Job | Tool | What it checks | | ||
| |---|---|---| | ||
| | `lychee` | [Lychee](https://lychee.cli.rs/) | External HTTP links (with caching, retries, rate-limit handling). Runs offline for PRs. | | ||
| | `broken-links-check` | Custom Python script (`detect_broken_links.py`) | Internal relative markdown links and symlinks. Creates GitHub annotations on PRs pointing to exact lines with broken links. | |
There was a problem hiding this comment.
We should probably get rid of these jobs entirely in another PR now
|
|
||
| ### Custom components | ||
|
|
||
| React components in `docs/components/` can be used in markdown via MDX. The |
There was a problem hiding this comment.
Let's link to fern's docs on custom components here: https://buildwithfern.com/learn/docs/customization/custom-react-components
| > [!NOTE] | ||
| > `fern docs dev` requires a valid `FERN_TOKEN` environment variable. Ask a | ||
| > maintainer for access, or set it in your shell profile: | ||
| > ```bash | ||
| > export FERN_TOKEN=<your-token> | ||
| > ``` |
There was a problem hiding this comment.
Is this true for doing fern docs dev locally? I thought it was only for publishing
|
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
|
Closing as this is pretty out of date |
Summary
mainvsdocs-website)fern check,fern docs broken-links,fern docs dev) including thefern/symlink requirementdynamo.docs.buildwithfern.com) and thatdocs.dynamo.nvidia.comis a custom domain aliasTest plan
fern checkpasses with the new page and nav entryfern docs broken-linksfinds no new broken linksSummary by CodeRabbit