fix: home hidden

Author: Kapil Gowru

.github/workflows/check-links.yml

@@ -19,7 +19,7 @@ jobs:
       - name: Install link checker
         run: pip install linkchecker
       - name: Create config
-        run: echo -e "[csv]\nseparator=,\n[filtering]\nignore=\n\texample.com\n\tus.i.posthog.com\n\tc.vialoops.com/CL0\n[output]\nignoreerrors=\n  ^http ^403 Forbidden" > lcconfig
+        run: echo -e "[csv]\nseparator=,\n[filtering]\nignore=\n\texample.com\n\tus.i.posthog.com\n\tdocs.stack-auth.com\n\tc.vialoops.com/CL0\n[output]\nignoreerrors=\n  ^http ^403 Forbidden" > lcconfig
       - name: Check ${{ matrix.site.name }} Links
         run: |
           set +e

fern/products/api-def/api-def.yml

@@ -14,7 +14,10 @@ navigation:
       - page: Authentication
         path: ./openapi-pages/auth.mdx
       - page: Servers
-        path: ./openapi-pages/servers.mdx            
+        path: ./openapi-pages/servers.mdx   
+      - page: Automation
+        path: ./openapi-pages/automation.mdx  
+        slug: sync-your-open-api-specification        
       - section: Endpoints
         slug: endpoints
         contents:
@@ -60,14 +63,7 @@ navigation:
           - page: Schema names
             path: ./openapi-pages/extensions/schema-names.mdx
           - page: Server names
-            path: ./openapi-pages/extensions/server-names.mdx
-      - section: Workflow & automation
-        skip-slug: true
-        contents:
-          - page: Overlay customizations
-            path: ./openapi-pages/overrides.mdx
-          - page: Sync your OpenAPI specification
-            path: ./openapi-pages/automation.mdx            
+            path: ./openapi-pages/extensions/server-names.mdx         
       - section: Integrate your server framework
         slug: frameworks
         contents:

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

@@ -3,28 +3,31 @@ title: Sync your OpenAPI Specification
 subtitle: Pull your latest OpenAPI Specification into your Fern Folder automatically.
 ---
 
-If you host your OpenAPI Specification at a publicly available URL, you can have Fern programmatically fetch the latest spec on a preconfigured cadence through the [sync-openapi GitHub Action](https://github.com/fern-api/sync-openapi). This ensures your committed OpenAPI spec stays up to date with your live API.
+Automatically pull your latest OpenAPI spec from a publicly available URL into your fern folder using the [sync-openapi GitHub Action](https://github.com/fern-api/sync-openapi). This keeps your committed spec in sync with your live API without manual updates.
+
 ## Setup
 <Steps>
   <Step title="Configure the origin URL">
    Add the origin field to your generators.yml to specify where your OpenAPI spec is hosted:
    ```yml title="generators.yml"
     api:
-      path: openapi/openapi.json
-      origin: https://api.example.com/openapi.json
+      specs: 
+        - openapi: .path/to/openapi.json               # Definition file
+          overrides: .path/to-openapi-overrides.yml    # Overrides file
+          origin: https://api.example.com/openapi.json # URL to fetch latest spec from
     ```
   </Step>
   <Step title="Add the GitHub Action">
     Create `.github/workflows/sync-openapi.yml` in your repository:
     ```yml
     name: Sync OpenAPI Specs # can be customized
     on:                               # additional custom triggers can be configured
-      workflow_dispatch:              # manual dispatch
+      workflow_dispatch:              # Manual trigger
       push:                                          
         branches:
-          - main                      # on push to main
+          - main                      # Trigger on push to
       schedule:
-        - cron: '0 3 * * *'           # everyday at 3:00 AM UTC
+        - cron: '0 3 * * *'           # Daily at 3:00 AM UTC
   jobs:
     update-from-source:
       runs-on: ubuntu-latest
@@ -42,13 +45,16 @@ If you host your OpenAPI Specification at a publicly available URL, you can have
             add_timestamp: true
 ```
   </Step>
-  <Step title="Add a GitHub token">
-    Generate a [fine-grained personal access token](https://github.com/settings/personal-access-tokens) with read/write access to your repository.
+  <Step title="Create a GitHub token">
+    Generate a [fine-grained personal access token](https://github.com/settings/personal-access-tokens) with **Contents** and **Pull requests** read/write permissions for your repository.
   </Step>
   <Step title="Add to Repository Secrets">
-    Navigate to your repository's `Settings > Secrets and variables > Actions`. Select **New repository secret**, name it `OPENAPI_SYNC_TOKEN`, add your token, and click **Add secret**.
+    In your repository, go to `Settings > Secrets and variables > Actions`. Click **New repository secret**, name it `OPENAPI_SYNC_TOKEN`, paste your token, and click **Add secret**.
   </Step>
 </Steps>
-By default, this will create daily PRs with API spec updates to the repo containing your fern folder. If you would like to adjust the frequency, learn more about GitHub's [schedule event](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule).
 
-<Info> For detailed configuration options and other use cases, see the [sync-openapi GitHub Action README](https://github.com/fern-api/sync-openapi). </Info>
+This creates daily pull requests with any API spec updates. To change the frequency, modify the `cron` schedule (see GitHub's [schedule syntax](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule)).
+
+## Other use cases 
+
+If your OpenAPI spec lives in a different repository (rather than at a public URL), you can sync it to your Fern folder using cross-repository sync. See the [sync-openapi GitHub Action README](https://github.com/fern-api/sync-openapi) for this and other advanced configurations. 

fern/products/docs/pages/api-references/customize-api-ref.mdx

@@ -9,7 +9,7 @@ When you [include an API in your `docs.yml` file](/learn/docs/api-references/gen
 If you are using an OpenAPI Specification, sections are created based on the `tags` property, converted to `lowerCamelCase` convention (e.g., createUser). If you are using a Fern Definition, sections are created based on the [`service`](/learn/api-definition/fern/endpoints#service-definition) file names.
 </Note>
 
-If you would like to only display a subset of endpoints, read more about the Audiences property for [OpenAPI Specifications](/learn/api-definition/openapi/audiences) or [Fern Definitions](/learn/api-definition/fern/audiences).
+If you would like to only display a subset of endpoints, read more about the Audiences property for [OpenAPI Specifications](/learn/api-definitions/openapi/extensions/audiences) or [Fern Definitions](/learn/api-definition/fern/audiences).
 
 ## Ordering the API Reference
 

fern/products/docs/pages/api-references/generate-websocket-ref.mdx

@@ -5,8 +5,6 @@ description: Learn how to generate and customize WebSocket API reference documen
 
 Fern generates WebSocket API reference documentation from your AsyncAPI specification or Fern Definition. The AsyncAPI specification describes message-driven APIs in a machine-readable format. Fern supports the [v2](https://www.asyncapi.com/docs/reference/specification/v2.x) and [v3](https://www.asyncapi.com/docs/reference/specification/v3.0.0) specifications.
 
-See [Deepgram's configuration](https://github.com/deepgram/deepgram-fern-config/blob/9a3d281d87963165df7cbb89c4883d5058abaf2e/fern/generators.yml#L5-L7) for a complete example.
-
 <Frame caption={<a href="https://developers.deepgram.com/reference/text-to-speech-api/speak-streaming">Example of how a WebSocket API Reference renders in Fern</a>}>
   <img src="websocket-deepgram.png" alt="WebSocket API Reference Example" />
 </Frame>

fern/products/docs/pages/changelog/2025-01-14.mdx

@@ -6,7 +6,7 @@ We're excited to announce compatibility with the `/llms.txt` [emerging standard]
 
 Both `/llms.txt` and `/llms-full.txt` are designed to be token-efficient, ensuring faster processing and cost-effective LLM interactions without sacrificing valuable info.
 
-If you use Fern Docs, this feature is auto-enabled like /robots.txt and /sitemap.xml. [Learn more](https://buildwithfern.com/learn/docs/developer-tools/llms-txt)
+If you use Fern Docs, this feature is auto-enabled like /robots.txt and /sitemap.xml. [Learn more](https://buildwithfern.com/learn/docs/seo/llms-txt)
 
 ![LLMs.txt Splash Image](./llms-txt.png)
 

fern/products/docs/pages/customization/search.mdx

@@ -23,7 +23,7 @@ If you are using the AI Search feature, the search box also functions as your si
 </Frame>
 
 <Note>
-    **Note:** If an article includes the `nofollow` or `noindex` [frontmatter](/learn/docs/content/frontmatter#indexing-properties), it will not be indexed by Algolia DocSearch and won't appear in search results.
+    **Note:** If an article includes the `nofollow` or `noindex` [frontmatter](/learn/docs/configuration/page-level-settings#indexing-properties), it will not be indexed by Algolia DocSearch and won't appear in search results.
 </Note>
 
 ## Integrating with Algolia

fern/products/docs/pages/developer-tools/gitlab.mdx

@@ -105,5 +105,5 @@ When finished, click **Create project access token**.
 Be sure to save the generated token - it won't be displayed after you leave the page. 
 </Note>
 ### Add token to repository variables
-You can do this using [the steps listed above](/learn/docs/developer-tools/gitlab#add-a-token-to-gitlab). 
+You can do this using [the steps listed above](/learn/docs/developer-tools/git-lab#add-a-token-to-gitlab). 
 </Steps>