Update 5.mdx based on issue #216

Author: kgowru

fern/products/docs/pages/changelog/2025/6/5.mdx

@@ -0,0 +1,61 @@
+---
+title: Support versions with products
+description: Adding API versioning to products in your Fern documentation
+---
+
+# Versioning Your Products
+
+You can add version support to products in your documentation by configuring versions in your `docs.yml` file. Each product can have multiple versions, making it easy for users to navigate between different API versions.
+
+## Add Versions to Products
+
+Add a `versions` array to each product in your `docs.yml` file:
+
+```yaml
+products:
+  - display-name: Data API
+    path: ./products/data/versions/v2.yml
+    subtitle: Integrate with our data platform
+    icon: fa-light fa-database
+    image: ./assets/product-selector/data-api-image.svg
+    slug: data
+    versions:
+      - display-name: v2
+        slug: v2.0.0
+        path: ./products/data/versions/v2.yml
+      - display-name: v2 (beta)
+        slug: v2.0.0-beta
+        path: ./products/data/versions/v2-beta.yml
+      - display-name: v1 (legacy)
+        slug: v1.0.0
+        path: ./products/data/versions/v1.yml
+```
+
+Each version requires:
+- `display-name`: The name shown in the version selector
+- `slug`: A URL-friendly identifier for the version
+- `path`: Path to the version's documentation files
+
+## Version Organization
+
+Best practices for organizing versioned documentation:
+
+1. Create a `versions` directory for each product
+2. Store each version's documentation in a separate YAML file
+3. Name files consistently (e.g., `v1.yml`, `v2.yml`)
+4. Use clear version labels that indicate status (e.g., "beta", "legacy")
+
+## Example Structure
+
+```
+docs/
+├── products/
+│   └── data/
+│       └── versions/
+│           ├── v1.yml
+│           ├── v2.yml
+│           └── v2-beta.yml
+└── docs.yml
+```
+
+The version selector will automatically appear in your documentation when versions are configured, allowing users to easily switch between different API versions.