From 4302f08d52ed70455ddd1dd9b0b4f1c7a5b0f587 Mon Sep 17 00:00:00 2001 From: Devin Logan Date: Sat, 21 Feb 2026 22:23:16 -0500 Subject: [PATCH 1/2] pro-->team for docs --- fern/products/api-def/asyncapi-pages/auth.mdx | 2 +- fern/products/api-def/asyncapi-pages/extensions/audiences.mdx | 2 +- fern/products/api-def/ferndef-pages/audiences.mdx | 2 +- fern/products/api-def/ferndef-pages/auth.mdx | 2 +- fern/products/api-def/ferndef-pages/endpoints/sse.mdx | 2 +- fern/products/api-def/openapi-pages/endpoints/sse.mdx | 2 +- fern/products/api-def/openapi-pages/extensions/audiences.mdx | 2 +- fern/products/dashboard/pages/pdf-export.mdx | 2 +- fern/products/docs/pages/api-references/audiences.mdx | 2 +- fern/products/docs/pages/ask-fern/api-get-started.mdx | 2 +- fern/products/docs/pages/authentication/password.mdx | 2 +- .../docs/pages/getting-started/setting-up-your-domain.mdx | 2 +- fern/products/docs/pages/integrations/feature-flags.mdx | 2 +- fern/products/docs/pages/navigation/products.mdx | 2 +- fern/products/docs/pages/navigation/versions.mdx | 2 +- fern/snippets/pro-plan.mdx | 2 +- fern/snippets/team-plan.mdx | 3 +++ 17 files changed, 19 insertions(+), 16 deletions(-) create mode 100644 fern/snippets/team-plan.mdx diff --git a/fern/products/api-def/asyncapi-pages/auth.mdx b/fern/products/api-def/asyncapi-pages/auth.mdx index f560bf3bd..3bc98ff89 100644 --- a/fern/products/api-def/asyncapi-pages/auth.mdx +++ b/fern/products/api-def/asyncapi-pages/auth.mdx @@ -141,7 +141,7 @@ components: ## OAuth2 security scheme - + OAuth2 authentication is supported for AsyncAPI specifications: diff --git a/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx b/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx index 305a5b455..9b051a964 100644 --- a/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx +++ b/fern/products/api-def/asyncapi-pages/extensions/audiences.mdx @@ -4,7 +4,7 @@ headline: Use audiences to filter your API (AsyncAPI) subtitle: Use `x-fern-audiences` to filter to relevant operations, channels and message schemas --- - + Audiences are a useful tool for segmenting your event-driven API for different consumers. Common examples of audiences include `public` and `beta`. diff --git a/fern/products/api-def/ferndef-pages/audiences.mdx b/fern/products/api-def/ferndef-pages/audiences.mdx index 06846941c..f125b560d 100644 --- a/fern/products/api-def/ferndef-pages/audiences.mdx +++ b/fern/products/api-def/ferndef-pages/audiences.mdx @@ -3,7 +3,7 @@ title: Audiences in Fern Definition subtitle: Use audiences in your Fern Definition to segment your API for different groups of consumers. --- - + Audiences are a useful tool for segmenting your API for different consumers. You can configure your Fern Docs to publish documentation specific to an `Audience`. You can use [audiences in your OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences), too. diff --git a/fern/products/api-def/ferndef-pages/auth.mdx b/fern/products/api-def/ferndef-pages/auth.mdx index 880c61291..19dc145b2 100644 --- a/fern/products/api-def/ferndef-pages/auth.mdx +++ b/fern/products/api-def/ferndef-pages/auth.mdx @@ -178,7 +178,7 @@ client = new Client({ ## OAuth client credentials - + If your API uses OAuth, you can specify an oauth scheme in `api.yml` and define a token retrieval endpoint in a separate `auth.yml` file ([example](https://github.com/fern-api/fern/blob/3137938b70e058f3691ddef34d5c1cc29acc4b80/test-definitions/fern/apis/oauth-client-credentials/definition/api.yml)). diff --git a/fern/products/api-def/ferndef-pages/endpoints/sse.mdx b/fern/products/api-def/ferndef-pages/endpoints/sse.mdx index a57e49e56..230bda3af 100644 --- a/fern/products/api-def/ferndef-pages/endpoints/sse.mdx +++ b/fern/products/api-def/ferndef-pages/endpoints/sse.mdx @@ -3,7 +3,7 @@ title: Server-sent events and streaming APIs subtitle: Use the `response-stream` key to model streaming endpoints --- - + Specifying `response-stream` on an endpoints allows you to represent endpoint responses that are streaming. diff --git a/fern/products/api-def/openapi-pages/endpoints/sse.mdx b/fern/products/api-def/openapi-pages/endpoints/sse.mdx index 95bc905b9..5d7e4af8d 100644 --- a/fern/products/api-def/openapi-pages/endpoints/sse.mdx +++ b/fern/products/api-def/openapi-pages/endpoints/sse.mdx @@ -39,7 +39,7 @@ components: ## Server-sent events - + If your API returns server-sent-events (SSE), with the `data` and `event` keys as seen below diff --git a/fern/products/api-def/openapi-pages/extensions/audiences.mdx b/fern/products/api-def/openapi-pages/extensions/audiences.mdx index 367aa8d36..153b4b0f2 100644 --- a/fern/products/api-def/openapi-pages/extensions/audiences.mdx +++ b/fern/products/api-def/openapi-pages/extensions/audiences.mdx @@ -4,7 +4,7 @@ headline: Use audiences to filter your API (OpenAPI) subtitle: Learn how to use x-fern-audiences to filter OpenAPI endpoints, schemas, and properties for different API consumers like public and beta users. --- - + Fern provides two ways to filter which API elements appear in your SDKs and API Reference docs: diff --git a/fern/products/dashboard/pages/pdf-export.mdx b/fern/products/dashboard/pages/pdf-export.mdx index 7a59c96e5..6b00ebb17 100644 --- a/fern/products/dashboard/pages/pdf-export.mdx +++ b/fern/products/dashboard/pages/pdf-export.mdx @@ -3,7 +3,7 @@ title: PDF export description: Export your documentation site as a PDF from the Fern Dashboard. --- - + Export your complete documentation site as a PDF directly from the [Fern Dashboard](https://dashboard.buildwithfern.com/). The generated PDF includes a cover page, table of contents with clickable links, and all content pages with headers and footers. diff --git a/fern/products/docs/pages/api-references/audiences.mdx b/fern/products/docs/pages/api-references/audiences.mdx index d3f9c0300..c9f804488 100644 --- a/fern/products/docs/pages/api-references/audiences.mdx +++ b/fern/products/docs/pages/api-references/audiences.mdx @@ -3,7 +3,7 @@ title: Audiences subtitle: Use audiences to filter the endpoints, schemas, and properties that are displayed in your API Reference. --- - + Audiences are a useful tool for segmenting your API for different consumers. Common examples of audiences include `public` and `beta`. You can configure audiences in both [the OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences) as well as [the Fern Definition](/learn/api-definition/fern/audiences). diff --git a/fern/products/docs/pages/ask-fern/api-get-started.mdx b/fern/products/docs/pages/ask-fern/api-get-started.mdx index 58b67dbd9..3b1e2a831 100644 --- a/fern/products/docs/pages/ask-fern/api-get-started.mdx +++ b/fern/products/docs/pages/ask-fern/api-get-started.mdx @@ -3,7 +3,7 @@ title: 'Introduction' subtitle: 'Welcome to the Fern API Reference.' --- - + The Fern AI API allows you to manage your Ask Fern configuration using Fern's public RESTful API. You can use the API to: diff --git a/fern/products/docs/pages/authentication/password.mdx b/fern/products/docs/pages/authentication/password.mdx index 8e5b20ac0..42e2a6f03 100644 --- a/fern/products/docs/pages/authentication/password.mdx +++ b/fern/products/docs/pages/authentication/password.mdx @@ -3,7 +3,7 @@ title: Password protection subtitle: Protect your documentation site with a shared password for simple access control. --- - + Password protection allows you to restrict access to your documentation site using a shared password. This is useful for pre-release documentation, internal resources, or any content you want to keep private without requiring individual user accounts. diff --git a/fern/products/docs/pages/getting-started/setting-up-your-domain.mdx b/fern/products/docs/pages/getting-started/setting-up-your-domain.mdx index b3aabffa4..c2428b86b 100644 --- a/fern/products/docs/pages/getting-started/setting-up-your-domain.mdx +++ b/fern/products/docs/pages/getting-started/setting-up-your-domain.mdx @@ -75,7 +75,7 @@ Once Fern has completed your setup, you'll be able to access your documentation - + To host your documentation on a subpath like `mydomain.com/docs`, you need to edit your `docs.yml` configuration and then get provider-specific instructions for setting up the subpath. Common providers include Cloudflare, AWS Route53 and Cloudfront, Netlify, and Vercel. diff --git a/fern/products/docs/pages/integrations/feature-flags.mdx b/fern/products/docs/pages/integrations/feature-flags.mdx index 89e7cf2c1..cccad7da5 100644 --- a/fern/products/docs/pages/integrations/feature-flags.mdx +++ b/fern/products/docs/pages/integrations/feature-flags.mdx @@ -4,7 +4,7 @@ subtitle: Control documentation visibility with LaunchDarkly description: Learn how to use Feature Flags in your Fern documentation --- - + Fern supports conditional rendering of documentation content using feature flags, powered by [LaunchDarkly](https://app.launchdarkly.com/signup) integration. Control visibility of documentation sections based on feature flag states for different release stages or user segments. diff --git a/fern/products/docs/pages/navigation/products.mdx b/fern/products/docs/pages/navigation/products.mdx index 4e02697e9..3875c18b3 100644 --- a/fern/products/docs/pages/navigation/products.mdx +++ b/fern/products/docs/pages/navigation/products.mdx @@ -3,7 +3,7 @@ title: Product switching subtitle: Learn how to configure product switching in Fern Docs. Set up multiple products with custom navigation, versioning, and styling options. --- - +