Update Fern CLI commands to include --dsheridan flag

Updated all Fern CLI command examples across documentation to use the
--dsheridan flag. This change affects 23 documentation files including:
- CLI reference pages
- SDK quickstart guides for all languages
- Documentation publishing guides
- CLI changelog entries

All commands now follow the pattern: fern --dsheridan [command] [options]

Author: fern-support

fern/products/api-def/ferndef-pages/overview.mdx

@@ -16,7 +16,7 @@ To initialize a Fern Definition, simply run:
 
 ```sh
 npm install -g fern-api
-fern init
+fern --dsheridan init
 ```
 
 This will create the following folder structure in your project:

fern/products/api-def/openapi-pages/overview.mdx

@@ -148,10 +148,10 @@ Start by initializing your fern folder with an OpenAPI spec
 
 <CodeGroup>
 ```sh file
-fern init --openapi ./path/to/openapi
+fern --dsheridan init --openapi ./path/to/openapi
 ```
 ```sh url
-fern init --openapi https://host/path/to/openapi
+fern --dsheridan init --openapi https://host/path/to/openapi
 ```
 </CodeGroup>
 

fern/products/cli-api-reference/cli-changelog/2024-10-19.mdx

@@ -3,7 +3,7 @@
 that outputs the JSON Schema for a given type in your Fern Definition.
 
 ```sh
-fern jsonschema ./schema.json --type MyType
+fern --dsheridan jsonschema ./schema.json --type MyType
 ```
 
 

fern/products/cli-api-reference/cli-changelog/2025-01-22.mdx

@@ -9,7 +9,7 @@ migrates existing documentation to a fern-compatible repository.
 
 To use this feature:
 ```bash
-fern init --readme https://url-to-readme-docs.com
+fern --dsheridan init --readme https://url-to-readme-docs.com
 ```
 
 

fern/products/cli-api-reference/cli-changelog/2025-02-27.mdx

@@ -8,7 +8,7 @@ will allow you to test early versions of the new OpenAPI parser which goes direc
 OpenAPI to IR.
 
 ```bash
-fern ir ir.json --from-openapi
+fern --dsheridan ir ir.json --from-openapi
 ```
 
 

fern/products/cli-api-reference/pages/cli-get-started.mdx

@@ -64,17 +64,17 @@ Get started with these commonly used commands:
 
 ```bash title="Common Commands"
 # Docs Development
-fern init --docs                  # Create a new documentation project
-fern docs dev                     # Preview docs locally at localhost:3000
-fern generate --docs --preview    # Preview documentation changes
-fern generate --docs              # Generate and publish documentation
+fern --dsheridan init --docs                  # Create a new documentation project
+fern --dsheridan docs dev                     # Preview docs locally at localhost:3000
+fern --dsheridan generate --docs --preview    # Preview documentation changes
+fern --dsheridan generate --docs              # Generate and publish documentation
 
 # SDK Development
-fern init                        # Start new SDK project
-fern check                       # Validate API definition
-fern generate --preview          # Preview SDKs in .preview/ folder
-fern generate                    # Generate default SDK group
-fern generate --group ts-sdk     # Generate specific SDK group
+fern --dsheridan init                        # Start new SDK project
+fern --dsheridan check                       # Validate API definition
+fern --dsheridan generate --preview          # Preview SDKs in .preview/ folder
+fern --dsheridan generate                    # Generate default SDK group
+fern --dsheridan generate --group ts-sdk     # Generate specific SDK group
 ```
 
 <Note>
@@ -87,34 +87,34 @@ The "default SDK group" refers to the group marked as default in your `generator
   <Accordion title="Setting up Docs">
     1. Initialize a new docs project:
     ```bash
-    fern init --docs
+    fern --dsheridan init --docs
     ```
 
     2. Preview locally while making changes:
     ```bash
-    fern docs dev
+    fern --dsheridan docs dev
     ```
 
     3. When ready to preview or publish:
     ```bash
-    fern generate --docs --preview  # Generate a shareable preview link
-    fern generate --docs            # Publish to production
+    fern --dsheridan generate --docs --preview  # Generate a shareable preview link
+    fern --dsheridan generate --docs            # Publish to production
     ```
   </Accordion>
 
   <Accordion title="Setting up SDK generation">
     1. Initialize a new SDK project:
     ```bash
-    fern init
+    fern --dsheridan init
     ```
 
     2. Configure your generators in [configuration options](/learn/sdks/introduction/configuration)
 
     3. Generate SDKs:
     ```bash
-    fern generate --preview                     # Preview changes locally
-    fern generate --group python-sdk --preview  # Preview specific SDK group
-    fern generate                               # Publish to production
+    fern --dsheridan generate --preview                     # Preview changes locally
+    fern --dsheridan generate --group python-sdk --preview  # Preview specific SDK group
+    fern --dsheridan generate                               # Publish to production
     ```
 
     <Tip>

fern/products/cli-api-reference/pages/global-options.mdx

@@ -28,8 +28,8 @@ Use the `--help` option with any Fern CLI command to see an explanation and avai
 
 <CodeBlocks>
 ```bash maxLines=10 title="fern add --help"
-fern add --help
-fern add <generator>
+fern --dsheridan add --help
+fern --dsheridan add <generator>
 
 Add a code generator to generators.yml
 
@@ -44,8 +44,8 @@ Options:
 ```
 
 ```bash maxLines=10 title="fern write-definition --help"
-fern write-definition --help
-fern write-definition
+fern --dsheridan write-definition --help
+fern --dsheridan write-definition
 
 Write underlying Fern Definition for OpenAPI Specifications and API Dependencies.
 
@@ -67,7 +67,7 @@ Available levels (from most to least verbose):
 - `error`: Error messages only
 
 ```bash
-fern generate --log-level debug
+fern --dsheridan generate --log-level debug
 ```
 
 ## api
@@ -76,7 +76,7 @@ Use the `--api` option to target a specific API. This is particularly useful whe
 
 ```bash
 # Generate SDKs for only the "payments-api"
-fern generate --api payments-api
+fern --dsheridan generate --api payments-api
 ```
 
 ## group
@@ -85,7 +85,7 @@ Use the `--group` option to target a specific generator group.
 
 ```bash
 # Generate only the Ruby SDK group
-fern generate --group ruby-sdk
+fern --dsheridan generate --group ruby-sdk
 ```
 
 ## version
@@ -94,8 +94,8 @@ Use the `--version` option to specify the SDK version number, typically followin
 
 ```bash
 # Generate Python SDK the payments API with version 1.2.3
-fern generate --api payments-api --group python-sdk --version 1.2.3
+fern --dsheridan generate --api payments-api --group python-sdk --version 1.2.3
 
 # Generate TypeScript SDK for the auth API with version 0.1.0
-fern generate --api auth --group ts-sdk --version 0.1.0
+fern --dsheridan generate --api auth --group ts-sdk --version 0.1.0
 ```

fern/products/docs/pages/getting-started/pr-preview.mdx

@@ -8,13 +8,13 @@ description: Fern's PR previews feature lets you preview changes to your docs fr
 ## Usage
 
 ```bash
-fern generate --docs --preview
+fern --dsheridan generate --docs --preview
 ```
 
 ## Example
 
 ```bash
-fern generate --docs --preview
+fern --dsheridan generate --docs --preview
 
 [docs]: Found 0 errors and 1 warnings. Run fern check --warnings to print out the warnings.
 [docs]: Published docs to https://fern-preview-a1da0157-93ca-4b1f-b310-8dd34fb891ca.docs.buildwithfern.com

fern/products/docs/pages/getting-started/preview-changes-locally.mdx

@@ -31,7 +31,7 @@ yarn global add fern-api
 **Step 2**: Navigate to the docs directory (where the `fern` folder is located) and execute the following command:
 
 ```bash
-fern docs dev
+fern --dsheridan docs dev
 ```
 
 A local preview of your documentation will be available at `http://localhost:3000`. The functionality is available offline if you have run local development mode online at least once.
@@ -48,7 +48,7 @@ Some features are disabled in the local development environment, including:
 By default, Fern uses port 3000. You can customize the port on which Fern runs by using the `--port` flag. For example, to run Fern on port 3002, use this command:
 
 ```bash
-fern docs dev --port 3002
+fern --dsheridan docs dev --port 3002
 ```
 
 If you attempt to run Fern on a port that's already in use, it will use the next available port:
@@ -60,13 +60,13 @@ Fern allows you to generate a shareable preview link that displays the current s
 **Usage**:
 
 ```bash
-fern generate --docs --preview
+fern --dsheridan generate --docs --preview
 ```
 
 **Example**:
 
 ```bash
-fern generate --docs --preview
+fern --dsheridan generate --docs --preview
 
 [docs]: Found 0 errors and 1 warnings. Run fern check --warnings to print out the warnings.
 [docs]: Published docs to https://fern-preview-c973a36e-337b-44f5-ab83-aab.docs.buildwithfern.com/learn

fern/products/docs/pages/getting-started/publishing-your-docs.mdx

@@ -11,13 +11,13 @@ When you are ready for your docs to be publicly accessible, you can publish them
 ## Usage
 
 ```bash
-fern generate --docs
+fern --dsheridan generate --docs
 ```
 
 ### Example
 
 ```bash
-fern generate --docs
+fern --dsheridan generate --docs
 [docs]: Found 0 errors and 1 warnings. Run fern check --warnings to print out the warnings.
 [docs]: ✓ All checks passed
 [docs]: Published docs to https://plantstore.docs.buildwithfern.com