# Unleash scales AI-ready documentation with Fern Docs

**Date:** 2026-05-12  
**Source:** https://buildwithfern.com/customers/unleash

> How Unleash migrated 300+ pages off Docusaurus in two weeks and made every doc AI-ready as half their traffic shifted to LLM tools.

---
<Eyebrow>The problem</Eyebrow>

## Unleash outgrew Docusaurus as their docs scaled and AI traffic surged

Unleash maintains hundreds of pages of documentation with a one-person documentation team. Their site was originally built on Docusaurus, but as their content grew, the platform started creating more friction than it solved.

Unleash's API reference depended on a third-party Docusaurus plugin that was clunky, kept getting flagged for security vulnerabilities, and once caused a bug obscure enough to take down the entire site search. Docusaurus's component library wasn't evolving and the platform didn't have the modern look Unleash wanted, so the team ended up building and maintaining custom solutions for features that should have been standard in a modern docs platform.

AI search was handled through Kapa, a third-party widget tucked away in a corner of the site. Discoverability was poor, and because it indexed on rendered HTML rather than source markdown, answer quality suffered. Meanwhile, roughly half of Unleash's documentation traffic was coming from AI tools, and Docusaurus had no native support for making content LLM-ready.

Unleash started using Fern for their documentation in January 2026. The migration consolidated hundreds of pages onto Fern Docs, giving the team a modern authoring experience and native AI capabilities that Docusaurus couldn't offer.

<Quote author="Melinda Fekete" role="Documentation Lead at Unleash">
  About 50% of our doc traffic now comes from AI tools. Fern nails the AI readiness piece better
  than any other docs platform we've seen.
</Quote>

<Eyebrow>The solution</Eyebrow>

## A modern docs platform built for humans and AI

Key capabilities Unleash unlocked with Fern:

- **Fast onboarding, minimal ramp-up.** Unleash migrated 300+ pages in about two weeks, largely because Fern's own documentation made the platform easy to learn. The authoring experience, writing in markdown with custom React components, was familiar enough that the team could focus on the migration itself rather than learning a new toolchain.
- **Less custom maintenance, more focus on content.** Unleash's docs serve a wide range of needs, including getting-started guides for developers new to feature management, detailed tutorials across 30+ SDKs, and comprehensive API reference documentation. On Docusaurus, the team was spending too much time building and maintaining custom components instead of focusing on that content. Fern's built-in component library covered those gaps with a modern design out of the box and a constantly expanding feature set, so the team isn't waiting on their docs platform to catch up with their needs.
- **A docs-as-code workflow anyone can contribute to.** When leadership or other stakeholders need to make a quick update, they use Fern Editor to jump in without touching the repo. Edits open a pull request automatically, keeping the docs-as-code workflow intact.
- **AI-native documentation, end to end.** Ask Fern replaced Unleash's third-party search widget with natively embedded AI search that actually gets used. Engagement and resolution rates both jumped significantly after the switch. Every page of Unleash documentation is also available as clean markdown with auto-generated llms.txt files, so the roughly 50% of Unleash's doc traffic coming from AI tools gets structured, LLM-ready content without any extra authoring effort. Language-specific filtering means AI coding tools only see what's relevant to the developer's stack.

<Eyebrow>Looking ahead</Eyebrow>

## Investing time in content quality, not platform upkeep

With Fern, the Unleash team gets granular visibility into how their docs are performing, including what users are searching for, what questions AI search can and can't resolve, and per-page feedback on whether content is actually helpful. With less time spent on platform maintenance, the team can act on those signals and continuously improve their docs based on real usage data.