You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each sub-path is published independently, but end users see a single unified site. The root `docs.nvidia.com` itself is a separate site outside the Fern setup — multi-source covers only the sub-paths. A Fern-published landing page is optional ([example](#example-setup-with-a-homepage-and-three-teams)), and any combination of sub-paths works, including just two.
28
+
Each sub-path is published independently, but end users see a single unified site. The root `docs.nvidia.com` itself is a separate site outside the Fern setup — multi-source covers only the sub-paths. A Fern-published landing page is optional ([example](#example-a-live-multi-source-site)), and any combination of sub-paths works, including just two.
29
29
30
30
## Set up multi-source docs
31
31
@@ -110,20 +110,35 @@ Two search modes are available:
110
110
111
111
</Steps>
112
112
113
-
## Example: Homepage and three sub-paths
113
+
## Example: A live multi-source site
114
114
115
-
This is the alternative shape to NVIDIA's setup: a Fern-managed homepage that serves as the root, with three product teams each on their own sub-path. Use this pattern when the root should be a landing page or product selector instead of pointing somewhere outside Fern.
115
+
<Tip>
116
+
Browse the live site at [multi-source.docs.buildwithfern.com](https://multi-source.docs.buildwithfern.com) and the source at [fern-api/docs-examples/multi-source](https://github.com/fern-api/docs-examples/tree/main/multi-source).
117
+
</Tip>
116
118
117
-
The setup uses four `fern/` projects — a homepage at `/home` plus one per team at `/seeds`, `/greenhouses`, and `/nursery`. All four share the same global theme (`plantstore-theme`) and set `multi-source: true`; they differ only in their basepath:
119
+
This is the alternative shape to NVIDIA's setup: a Fern-managed homepage at the bare root, plus team sub-paths underneath. The example uses six independent `fern/` projects on one shared domain — a homepage at `/`, a `/seeds` team hub with two nested sub-children, and standalone `/greenhouses` and `/nursery` teams:
120
+
121
+
```
122
+
multi-source.docs.buildwithfern.com
123
+
├── / ← homepage
124
+
├── /seeds ← Seeds team hub
125
+
│ ├── /seeds/sunflower ← Sunflower sub-team
126
+
│ └── /seeds/tomato ← Tomato sub-team
127
+
├── /greenhouses ← Greenhouses team
128
+
└── /nursery ← Nursery team
129
+
```
130
+
131
+
All six projects share `global-theme: plantstore-theme` and set `multi-source: true` — they differ only in their basepath. Sub-paths can themselves contain nested sub-paths: `/seeds/sunflower` and `/seeds/tomato` are independently published projects that live under `/seeds`.
132
+
133
+
The example uses Fern's preview domain (`*.docs.buildwithfern.com`), so no `custom-domain` is set. A production deployment typically adds `custom-domain: docs.example.com/...` to each instance.
118
134
119
135
<Tabs>
120
136
<Tabtitle="Homepage">
121
-
```yamlHomepage — docs.yml
137
+
```yamlhomepage/fern/docs.yml
122
138
global-theme: plantstore-theme
123
139
124
140
instances:
125
-
- url: plantstore.docs.buildwithfern.com/home
126
-
custom-domain: docs.plantstore.com/home
141
+
- url: multi-source.docs.buildwithfern.com
127
142
multi-source: true
128
143
129
144
navigation:
@@ -135,25 +150,24 @@ The homepage `home.mdx` can use cards to direct users to each team's docs:
0 commit comments