Small updates/additions to existing publishing pages (#383)

devalog · web-flow · commit 296a938f0e93 · 2025-08-07T13:01:45.000-04:00
diff --git a/fern/products/sdks/overview/csharp/publishing-to-nuget.mdx b/fern/products/sdks/overview/csharp/publishing-to-nuget.mdx
@@ -18,66 +18,39 @@ you'll have a versioned package published on NuGet.
 
 <Steps>
 
-	<Step title="Run `fern add <generator>`">
+	<Step title="Configure `output` location">
 
-	  Navigate to your `generators.yml` on your local machine. Your `generators.yml` lives inside of your `fern` folder and contains all the configuration for your Fern generators. 
+	Next, change the output location in `generators.yml` from `local-file-system` (the default) to `nuget` to indicate that Fern should publish your package directly to the NuGet registry:
 
-	  Add a new generator to `generators.yml`:
+	```yaml {6-7}
+	groups: 
+		csharp-sdk:
+		generators:
+			- name: fernapi/fern-csharp-sdk
+			version: <Markdown src="/snippets/version-number-csharp.mdx"/>
+			output:
+				location: nuget
 
+	```
+	</Step>
 
-	    ```bash
-	    fern add fern-csharp-sdk --group csharp-sdk
-	    ```
-
-	  Once the command completes, you'll see a new group created in your `generators.yml`:
-
-	  ```yaml {3-9}
-	    groups:
-	    ...
-	      csharp-sdk:
-	        generators:
-	          - name: fernapi/fern-csharp-sdk
-	            version: <Markdown src="/snippets/version-number-csharp.mdx"/>
-	            output:
-	              location: local-file-system
-	              path: ../sdks/csharp
-	    ```
-
-	  </Step>
-
-	  <Step title="Configure `output` location">
-
-		Next, change the output location in `generators.yml` from `local-file-system` (the default) to `nuget` to indicate that Fern should publish your package directly to the NuGet registry:
-
-	    ```yaml {6-7}
-	    groups: 
-	      csharp-sdk:
-	        generators:
-	          - name: fernapi/fern-csharp-sdk
-	            version: <Markdown src="/snippets/version-number-csharp.mdx"/>
-	            output:
-	              location: nuget
-
-	    ```
-	  </Step>
-
-	  <Step title="Add a unique package name">
+	<Step title="Add a unique package name">
 
-	     Your package name must be unique in the NuGet repository, otherwise publishing your SDK to NuGet will fail. Update your package name if you haven't done so already:
+		Your package name must be unique in the NuGet repository, otherwise publishing your SDK to NuGet will fail. Update your package name if you haven't done so already:
 
 
-```yaml {8}
-groups: 
-  csharp-sdk:
-    generators:
-      - name: fernapi/fern-csharp-sdk
-        version: <Markdown src="/snippets/version-number-csharp.mdx"/>
-        output:
-          location: nuget
-          package-name: your-package-name
-```
-	    
-	  </Step>
+	```yaml {8}
+	groups: 
+	csharp-sdk:
+		generators:
+		- name: fernapi/fern-csharp-sdk
+			version: <Markdown src="/snippets/version-number-csharp.mdx"/>
+			output:
+			location: nuget
+			package-name: your-package-name
+	```
+	
+	</Step>
 	<Step title="Configure `client-class-name`">
 
 	     The `client-class-name` option controls the name of the generated client. This is the name customers use to import your SDK (`import { your-client-name } from 'your-package-name';`). 
diff --git a/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx b/fern/products/sdks/overview/go/publishing-to-go-package-manager.mdx
@@ -25,35 +25,6 @@ you'll have a versioned package published on pkg.go.dev.
 
 <Steps>
 
-	<Step title="Run `fern add <generator>`">
-
-	  Navigate to your `generators.yml` on your local machine. Your `generators.yml` lives inside of your `fern` folder and contains all the configuration for your Fern generators. 
-
-	  Add a new generator to `generators.yml`:
-
-
-	    ```bash
-	    fern add fern-go-sdk --group go-sdk
-	    ```
-
-	  Once the command completes, you'll see a new group created in your `generators.yml`:
-
-    ```yaml {2-11}
-    groups:
-      go-sdk:
-        generators:
-          - name: fernapi/fern-go-sdk
-            version: <Markdown src="/snippets/version-number-go.mdx"/>
-            output:
-              location: local-file-system
-              path: ../sdks/go
-            config:
-              module:
-                path: sdk
-    ```
-
-	  </Step>
-
 	  <Step title="Configure `output` location">
 
         Go publishes via Git repositories, so remove the auto-generated
diff --git a/fern/products/sdks/overview/java/publishing-to-maven-central.mdx b/fern/products/sdks/overview/java/publishing-to-maven-central.mdx
@@ -13,32 +13,6 @@ page, you'll have a versioned package published on Maven Central.
 
 <Steps>
 
-	<Step title="Run `fern add <generator>`">
-
-	  Navigate to your `generators.yml` on your local machine. Your `generators.yml` lives inside of your `fern` folder and contains all the configuration for your Fern generators. 
-
-	  Add a new generator to `generators.yml`:
-
-
-	    ```bash
-	    fern add fern-java-sdk --group java-sdk
-	    ```
-
-	  Once the command completes, you'll see a new group created in your `generators.yml`:
-
-	  ```yaml {2-8}
-	    groups:
-	      java-sdk:
-	        generators:
-	          - name: fernapi/fern-java-sdk
-	            version: <Markdown src="/snippets/version-number-java.mdx"/>
-	            output:
-	              location: local-file-system
-	              path: ../sdks/java/src/main/java/
-	    ```
-
-	  </Step>
-
 	  <Step title="Configure `output` location">
 
 		Next, change the output location in `generators.yml` from `local-file-system` (the default) to `maven` to indicate that Fern should publish your package directly to the Maven Central registry:
@@ -142,35 +116,38 @@ groups:
           repository: your-org/company-java
 ```
 	</Step>
+</Steps>
 
-    <Step title="Generate GPG Signature">
+## Generate GPG Signature
 
-    Next, set up code signing credentials by generating or identifying a GPG key ID, password, and secret key.  Maven Central requires all artifacts to be digitally signed with PGP/GPG keys.
+  Next, set up code signing credentials by generating or identifying a GPG key ID, password, and secret key.  Maven Central requires all artifacts to be digitally signed with PGP/GPG keys.
 
 <Info>If you don't have gpg installed, you can download the binary from [https://gnupg.org/download/index.html](https://gnupg.org/download/index.html), or install it via package manager.</Info>
-
-1. Find your key
-    * If you already have a GPG key, you can list your keys:
+<Steps>
+<Step title="Find your key">
+    If you already have a GPG key, you can list your keys:
 
         ```sh
         gpg --list-secret-keys --keyid-format LONG
         ```
 
-    * If you don't have a GPG key, you can generate a new one:
+    If you don't have a GPG key, you can generate a new one:
 
         ```sh
         gpg --gen-key
         ```
         
         You'll be prompted to create a new username and passphrase. 
+</Step>
+<Step title="Export your key">
 
-1. To export your secret key, run:
+Export your key so you can store it in an environment variable later on:
 
     ```sh
-    gpg --export-secret-keys --armor KEY_ID
+    gpg --export-secret-keys --armor YOUR_KEY_ID
     ```
 
-    Be sure to replace `KEY_ID` with the key ID of the key you want to export.
+    Be sure to replace `YOUR_KEY_ID` with the key ID of the key you want to export.
 
     <Info>More information is available on [Maven Central's GPG validation page](https://central.sonatype.org/publish/requirements/gpg/).</Info>
 </Step>
@@ -197,6 +174,17 @@ groups:
           repository: your-org/company-java
 ```
 </Step>
+<Step title="Upload your key to public key servers">
+
+Finally, upload your key to public key servers so Maven Central can access the signature:
+
+  ```bash
+  # Upload to multiple key servers
+  gpg --keyserver keyserver.ubuntu.com --send-keys YOUR_KEY_ID
+  gpg --keyserver keys.openpgp.org --send-keys YOUR_KEY_ID
+  gpg --keyserver pgp.mit.edu --send-keys YOUR_KEY_ID
+```
+</Step>
 </Steps>
 
 ## Release your SDK to Maven Central
diff --git a/fern/products/sdks/overview/php/publishing-to-packagist.mdx b/fern/products/sdks/overview/php/publishing-to-packagist.mdx
@@ -17,33 +17,6 @@ you'll have a versioned package published on Packagist.
 
 <Steps>
 
-	<Step title="Run `fern add <generator>`">
-
-	  Navigate to your `generators.yml` on your local machine. Your `generators.yml` lives inside of your `fern` folder and contains all the configuration for your Fern generators. 
-
-	  Add a new generator to `generators.yml`:
-
-
-	    ```bash
-	    fern add fern-php-sdk --group php-sdk
-	    ```
-
-	  Once the command completes, you'll see a new group created in your `generators.yml`:
-
-	  ```yaml {2-8}
-      groups: 
-        php-sdk:
-          generators:
-            - name: fernapi/fern-php-sdk
-              version: <Markdown src="/snippets/version-number.mdx"/>
-	          output:
-	            location: local-file-system
-	            path: ../sdks/php
-	    ```
-
-	  </Step>
-
-
 	  <Step title="Add repository location">
 
 	  PHP publishes via Git repositories, so remove the auto-generated `output`, `location`, and `path` fields. Instead, add the path to your GitHub repository: 
diff --git a/fern/products/sdks/overview/python/publishing-to-pypi.mdx b/fern/products/sdks/overview/python/publishing-to-pypi.mdx
@@ -17,33 +17,6 @@ you'll have a versioned package published on PyPI.
 
 <Steps>
 
-	<Step title="Run `fern add <generator>`">
-
-	  Navigate to your `generators.yml` on your local machine. Your `generators.yml` lives inside of your `fern` folder and contains all the configuration for your Fern generators. 
-
-	  Add a new generator to `generators.yml`:
-
-
-	    ```bash
-	    fern add fern-python-sdk --group python-sdk
-	    ```
-
-	  Once the command completes, you'll see a new group created in your `generators.yml`:
-
-	  ```yaml {3-9}
-	    groups:
-	    ...
-	      python-sdk:
-	        generators:
-	          - name: fernapi/fern-python-sdk
-	            version: <Markdown src="/snippets/version-number-python.mdx"/>
-	            output:
-	              location: local-file-system
-	              path: ../sdks/python
-	    ```
-
-	  </Step>
-
 	  <Step title="Configure `output` location">
 
 		Next, change the output location in `generators.yml` from `local-file-system` (the default) to `pypi` to indicate that Fern should publish your package directly to the PyPI registry:
diff --git a/fern/products/sdks/overview/ruby/publishing-to-rubygems.mdx b/fern/products/sdks/overview/ruby/publishing-to-rubygems.mdx
@@ -13,33 +13,6 @@ you'll have a versioned package published on RubyGems.
 
 <Steps>
 
-	<Step title="Run `fern add <generator>`">
-
-	  Navigate to your `generators.yml` on your local machine. Your `generators.yml` lives inside of your `fern` folder and contains all the configuration for your Fern generators. 
-
-	  Add a new generator to `generators.yml`:
-
-
-	    ```bash
-	    fern add fern-ruby-sdk --group ruby-sdk
-	    ```
-
-	  Once the command completes, you'll see a new group created in your `generators.yml`:
-
-	  ```yaml {3-9}
-	    groups:
-	    ...
-	      ruby-sdk:
-	        generators:
-	          - name: fernapi/fern-ruby-sdk
-	            version: <Markdown src="/snippets/version-number-ruby.mdx"/>
-	            output:
-	              location: local-file-system
-	              path: ../sdks/ruby
-	    ```
-
-	  </Step>
-
 	  <Step title="Configure `output` location">
 
 		Next, change the output location in `generators.yml` from `local-file-system` (the default) to `pypi` to indicate that Fern should publish your package directly to the PyPI registry:
