add redirects best practices and info on default version

Author: devalog

fern/products/docs/pages/navigation/products.mdx

@@ -188,6 +188,8 @@ products:
 ```
 </CodeBlock>
 
+<Markdown src="/snippets/default-version.mdx" />
+
 </Step>
 <Step title="Indicate availability">
 

fern/products/docs/pages/navigation/versions.mdx

@@ -44,7 +44,7 @@ Version-specific `yml` files:
 </Step>
 <Step title="Add your version configuration">
 
-Define a version in the top-level `docs.yml` by adding an item to the `versions` list and specifying the `display-name` and `path`. 
+Define a version in the top-level `docs.yml` by adding an item to the `versions` list and specifying the `display-name` and `path`.
 
 <CodeBlock title="docs.yml">
 ```yaml
@@ -55,6 +55,9 @@ versions:
     path: ./versions/v2.yml
 ```
 </CodeBlock>
+
+<Markdown src="/snippets/default-version.mdx" />
+
 </Step>
 <Step title="Indicate availability">
 

fern/snippets/default-version.mdx

@@ -0,0 +1,4 @@
+<Note title="Default versions">
+
+  Versions appear in the version dropdown in the order listed in `versions`. The first version in your `versions` list is your default version. This version appears at unversioned paths like `/docs/getting-started`, while other versions use versioned paths like `/docs/getting-started/v2`. Fern automatically handles version routing by [redirecting](/docs/seo/redirects) broken versioned links to the default version and managing canonical URLs.
+</Note>

fern/snippets/redirects.mdx

@@ -1,6 +1,6 @@
 The `redirects` object allows you to redirect traffic from one path to another. You can redirect exact paths or use dynamic patterns with [`regex`](https://www.npmjs.com/package/path-to-regexp) parameters like `:slug` to handle bulk redirects. You can redirect to internal paths within your site or external URLs.
 
-If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include the subpath in both the source and destination paths.
+If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include the subpath in both the source and destination paths. 
 
 
   <CodeBlock title="docs.yml">
@@ -38,3 +38,42 @@ If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include t
 <ParamField path="permanent" type="boolean" required={false}>
   Toggle between **permanent** and **temporary** redirects (default `false`). When true, the status code is 308. When false, the status code is 307.
 </ParamField>
+
+### Best practices
+
+Only add redirects when necessary. Having a long list of redirects can slow down your site since each request must check against all redirect rules before routing the user.
+
+Avoid using redirects for 404 handling or versioning behavior, as Fern provides built-in settings for these use cases.
+
+<AccordionGroup>
+<Accordion title="404 handling">
+
+Don't create redirects to send broken links to your homepage:
+
+```yaml title="docs.yml"
+redirects:
+  - source: /docs/event-notifications
+    destination: / # Don't do this
+```
+
+Instead, reach out to Fern to enable automatic homepage redirects, an internal setting that handles broken links without needing manual redirects.
+
+</Accordion>
+<Accordion title="Versioning and redirects">
+
+If you have [versions](/docs/configuration/versions) configured, your default version uses unversioned paths (`/docs/getting-started`), while other versions use versioned paths (`/docs/getting-started/v2`). Fern automatically handles version routing by redirecting broken versioned links to the default version and managing canonical URLs.
+
+Avoid redirecting from unversioned to versioned URLs:
+
+```yaml title="docs.yml"
+redirects:
+  - source: /docs/event-notifications
+    destination: /docs/event-notifications/v2 # Don't do this
+```
+
+This breaks Fern's version switcher behavior, potentially creating redirect loops or preventing users from navigating between versions.
+
+If you frequently need to redirect from the default version to another version, consider changing which version is set as default in your versions configuration.
+
+</Accordion>
+</AccordionGroup>