chore: set up control repo for theme upload and edits#1885
chore: set up control repo for theme upload and edits#1885fern-support wants to merge 2 commits intoNVIDIA-NeMo:mainfrom
Conversation
Greptile SummaryThis PR establishes the NeMo Curator repo as the Fern "control" repo for uploading and managing the shared
Confidence Score: 4/5Safe to merge for NeMo Curator itself, but theme.yml contains NeMo Curator-specific logo values that will break branding on other child repos the moment the theme is uploaded and inherited. One P1 finding: logo.href and logo.right-text in the shared theme are product-specific; every other child repo inheriting the nvidia global theme will display NeMo Curator branding. This should be fixed before running fern docs theme upload --name nvidia. fern/theme/theme.yml (product-specific logo values in a shared global theme) Important Files Changed
|
| .hero-column-title { | ||
| font-size: 20px; | ||
| } | ||
|
|
||
| .hero-column-subtitle { | ||
| font-size: 14px; | ||
| } | ||
|
|
There was a problem hiding this comment.
Ephemeral Figma MCP asset URL used as mask-image
https://www.figma.com/api/mcp/asset/... is a Figma MCP API path that is not a stable public CDN URL — it may expire with the session, become inaccessible due to CORS, or disappear when the asset is moved. When this URL fails, the mask-image silently has no effect, breaking the .landing-gradient-bottom visual. Replace it with a self-hosted or CDN-hosted SVG asset (e.g. alongside the other NVIDIA SVGs in fern/theme/assets/assets/).
Establishes this repo as the "control" repo for theme upload and edits. Edit all canonical assets for thematic elements here, and then run
fern docs theme upload --name nvidiawhen you'd like to push up edits to be hosted by Fern.Children NVIDIA documentation repos can then simply inherit the thematic elements by specifying the global theme name
nvidiain theirdocs.yml.Full documentation: https://buildwithfern.com/learn/docs/customization/global-themes