For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Getting started
    • Overview
    • How it works
    • Quickstart
    • Project structure
    • Customer showcase
    • Changelog
  • Configuration
    • Overview
    • Site-level settings
    • Page-level settings
  • Writing content
    • Markdown basics
    • Rich media in Markdown
    • Fern Editor
    • Reusable snippets
  • AI features
    • Overview
    • Fern Writer
    • AI-generated examples
    • Markdown access
      • Overview
      • Customize LLM output
      • Agent directives
      • Analytics and integration
    • MCP server
    • API catalog discovery
      • Orchestrate GitHub releases
      • Auto-update last updated dates
      • Cursor
      • GitLab
      • Vale
      • Download OpenAPI spec
      • Download AsyncAPI spec
  • Public API
    • GETJWT from Fern API key
    • GETAlgolia search credentials
    • GETCurrent user information
  • Fern Writer API
    • GETGet Fern Writer Install Link
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
On this page
  • Setup
Developer tools

Using Vale

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Hosting with GitLab

Next

Download OpenAPI spec

Vale is an open-source linting tool that helps maintain consistent writing style and catch common errors in documentation.

Use Vale with your Fern docs to automatically check for style issues and enforce writing guidelines. Vale runs locally or in CI/CD to catch issues before they’re published.

Setup

1

Install Vale

Install Vale on your local machine.

2

Create a .vale.ini file in your repository root

Create a .vale.ini file and add the following to it so Vale parses MDX files as Markdown:

vale.ini
[formats]
mdx = md
3

Add style rules

Import existing Vale style packages or create your own style rules.

4

Check your docs

Check your entire documentation set, all pages in a directory, or a specific page:

$vale fern/
$vale fern/pages/payments/
$vale fern/pages/payments/overview.mdx
5

Disable Vale for certain kinds of content

To disable Vale in specific sections of your Fern docs, use Vale comments wrapped in MDX syntax. This is particularly useful for code blocks, where Vale might flag variable names or code syntax as style violations.

Example Vale Usage
1Vale will check this text.
2
3{/* <!-- vale off --> */}
4
5Vale won't check this text
6
7<CodeBlock>
8```typescript
9import { PlantClient } from "@plantstore/sdk";
10
11const client = new PlantClient({ apiKey: "YOUR_API_KEY" });
12const plant = await client.createPlant({
13 name: "Monstera",
14 species: "Monstera deliciosa"
15});
16```
17</CodeBlock>
18
19{/* <!-- vale on --> */}
20
21Vale will start checking this text again.
6

Automate Vale (optional)

Consider integrating Vale into your workflow so it runs automatically for all contributors:

  • GitHub Actions: Use the Vale Action to run Vale on pull requests and add inline comments on style issues
  • Pre-commit hooks: Use Vale’s pre-commit integration to check files before they’re committed

This helps enforce consistent style standards across your documentation team without requiring manual Vale runs.