feat: moved over all docs content

Author: Kapil Gowru

fern/products/docs/docs.yml

@@ -90,51 +90,39 @@ navigation:
       - page: Hiding Content
         path: ./pages/navigation/hiding-content.mdx
   - section: API References
+    collapsed: true
     contents:
       - page: Generate API Reference
-        icon: fa-regular fa-wand-sparkles
         path: ./pages/api-references/generate-api-ref.mdx
         slug: generate-api-ref
       - page: SDK Snippets
-        icon: fa-regular fa-brackets-curly
         path: ./pages/api-references/sdk-snippets.mdx
       - page: HTTP Snippets
-        icon: fa-regular fa-code
         path: ./pages/api-references/http-snippets.mdx
       - section: API Explorer
         slug: api-explorer
         path: ./pages/api-references/api-explorer.mdx
-        icon: fa-regular fa-play
         contents:
           - page: Auto-populate API Keys
-            icon: fa-regular fa-key
             path: ./pages/api-references/autopopulate-api-key.mdx
       - page: Endpoint Errors
-        icon: fa-regular fa-triangle-exclamation
         path: ./pages/api-references/endpoint-errors.mdx
       - page: Audiences
-        icon: fa-regular fa-user-group
         path: ./pages/api-references/audiences.mdx
       - page: Customize API Reference Layout
-        icon: fa-regular fa-arrows-up-down-left-right
         path: ./pages/api-references/customize-api-ref.mdx
       - page: Write Markdown in API Reference
-        icon: fa-regular fa-pencil
         path: ./pages/api-references/api-ref-content.mdx
       - page: Generate Webhook Reference
-        icon: fa-regular fa-webhook
         path: ./pages/api-references/generate-webhook-ref.mdx
       - page: Multiple Server URLs
-        icon: fa-regular fa-server
         path: ./pages/api-references/server-urls.mdx
         slug: server-urls
       - page: Generate WebSocket Reference
-        icon: fa-regular fa-plug
         path: ./pages/api-references/generate-websocket-ref.mdx
         slug: generate-websocket-ref
       - page: Generate OpenRPC Reference
-        icon: fa-regular fa-diamond
-        path: ./pages/api
+        path: ./pages/api-references/generate-openrpc-ref.mdx
         slug: generate-openrpc-ref
   - section: SEO
     collapsed: true
@@ -143,8 +131,6 @@ navigation:
         path: ./pages/seo/configuring-slugs.mdx
       - page: Redirects
         path: ./pages/seo/redirects.mdx
-      - page: SEO Metadata
-        path: ./pages/seo/seo-metadata.mdx
       - page: llms.txt
         path: ./pages/seo/llms-txt.mdx
   - section: Authentication
@@ -155,7 +141,7 @@ navigation:
       - page: RBAC
         path: ./pages/authentication/rbac.mdx
       - page: API Key Injection
-        path: ./pages/authentication/api-key-injection.mdx
+        path: ./pages/api-references/autopopulate-api-key.mdx
   - section: Enterprise
     collapsed: true
     contents:
@@ -164,6 +150,8 @@ navigation:
   - section: Integrations
     collapsed: true
     contents:
+      - page: Overview
+        path: ./pages/integrations/overview.mdx
       - section: Analytics
         contents:
           - page: Google
@@ -174,16 +162,27 @@ navigation:
             path: ./pages/integrations/analytics/fullstory.mdx
           - page: Segment
             path: ./pages/integrations/analytics/segment.mdx
+          - page: Mixpanel
+            path: ./pages/integrations/analytics/mixpanel.mdx
       - section: Support
         contents:
-          - page: Postman
-            path: ./pages/integrations/support/postman.mdx
+          - page: Intercom
+            path: ./pages/integrations/support/intercom.mdx
       - page: Postman
         path: ./pages/integrations/postman.mdx
-      - page: Feature Flags
-        path: ./pages/integrations/feature-flags.mdx
-      - page: Self-hosted
-        path: ./pages/integrations/self-hosted.mdx
+      - page: LaunchDarkly Feature Flags 
+        path: ./pages/integrations/launchdarkly.mdx
+  - section: Developer Tools
+    collapsed: true
+    contents:
+      - page: Cursor
+        path: ./pages/developer-tools/cursor.mdx
+      - page: GitLab
+        path: ./pages/developer-tools/gitlab.mdx
+      - page: Vale
+        path: ./pages/developer-tools/vale.mdx  
+      - page: View Markdown
+        path: ./pages/developer-tools/view-markdown.mdx
   - changelog: ./pages/changelog
     icon: fa-regular fa-clock-rotate-left
 

fern/products/docs/pages/api-references/alchemy-openrpc.png

@@ -0,0 +1,39 @@
+---
+title: Generate OpenRPC Reference
+description: Learn how to generate and customize OpenRPC API reference documentation
+---
+
+Fern enables you to generate professional, interactive API reference documentation for your JSON-RPC APIs using the [OpenRPC](https://open-rpc.org/) specification. OpenRPC provides a standardized, machine-readable format for describing JSON-RPC 2.0 APIs, unlocking powerful documentation and code generation workflows.
+
+<Frame caption={<a href="https://www.alchemy.com/docs/data/nft-api/api-reference/nft-ownership-endpoints/get-nf-ts-for-owner-v-3">Example of Alchemy's docs site</a>}>
+  <img src="./alchemy-openrpc.png" alt="Alchemy's OpenRPC API Reference Example" />
+</Frame>
+
+## How to Add an OpenRPC Endpoint
+
+1. Add your OpenRPC specification file (e.g., `openrpc.yaml`) to your `/fern` directory.
+2. Configure your `generators.yml` to point to your OpenRPC spec:
+
+<CodeBlock title='generators.yml'>
+  ```yaml
+  api:
+    specs:
+      - openrpc: ../../api-specs/openrpc/wallet.yml
+  ```
+</CodeBlock>
+
+### Configuration Properties
+
+<ParamField path="api.specs[].openrpc" required>
+  Path to your OpenRPC specification file. You can include multiple OpenRPC specs if your project exposes more than one JSON-RPC API.
+</ParamField>
+
+## Common Use Cases
+
+JSON-RPC APIs are widely used for:
+- **Blockchain & Crypto**: Node RPC endpoints, wallet APIs
+- **FinTech**: Trading platforms, market data feeds
+- **Developer Tools**: Language servers, debuggers, automation
+- **Distributed Systems**: Remote procedure calls between services
+
+Leverage Fern and OpenRPC to deliver world-class developer experiences for your JSON-RPC APIs.

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

@@ -1,7 +1,73 @@
 ---
-title: Role-Based Access Control
+title: Role-based access control
+subtitle: Control who can view your documentation
+description: Learn how to restrict access to your documentation using role-based access control (RBAC)
 ---
 
-How to implement role-based access control for your documentation.
+<Note>RBAC is part of the pro plan.</Note>
 
-<Warning>This page is a WIP, please refer to our previous [documentation](https://buildwithfern.com/learn/docs/getting-started/overview).</Warning> 
+Fern allows you to restrict parts of your navigation to individuals with specific roles. Below, we walk through each of the steps
+required to configure RBAC.
+
+<Steps>
+### Define all the `roles` in your docs.yml
+
+Start by defining all the different roles in your `docs.yml`. You can simply specify this under a `roles` key:
+
+```yml docs.yml
+roles:
+  - everyone # every user is given this role
+  - partners
+  - beta-users
+  - admins
+```
+
+<Info>The `everyone` role is a special role. Every user has this role.</Info>
+
+### Define viewers on parts of the navigation
+
+Every navigation item (`sections`, `pages`, `api references`) can have a set of designated viewers. If you don't
+specify viewers, then it defaults to `everyone` and the page is public.
+
+```yml docs.yml {7-8,14-16}
+navigation:
+  - tab: Documentation
+    layout:
+      - page: Overview
+        path: pages/overview.mdx
+      - section: Beta Release
+        viewers:
+          - beta-users
+  - tab: API Reference
+    layout:
+      - page: Overview
+        path: pages/overview.mdx
+      - section: Beta Release
+        viewers:
+          - partners
+          - admin
+```
+
+The viewers are inherited by nested pieces of content. For example, if a section can only be viewed by `admins`, then all its
+pages and nested sections can also only be viewed by admins.
+
+### Configure authentication via a `fern_token`
+
+In this step, we will configure authentication so that Fern can understand what roles a particular user has. Fern expects the user's
+browser session to have a cookie called `fern_token`. If the cookie is not present, the user will be redirected to your company's
+login page.
+
+Upon login, you must set a JWT for the user using a secret key that we will provide you with. The JWT must have a `fern` claim
+with a key called roles.
+
+```json
+{
+  "fern": {
+    "roles": ["partners"]
+  }
+}
+```
+
+<Note>Please reach out to [email protected] when you are on this step so we can provide you with a secret key.</Note>
+
+</Steps>