Custom React components

View as Markdown
Pro and Enterprise feature

This feature is available only for the Pro and Enterprise plans. To get started, reach out to support@buildwithfern.com.

You can extend Fern’s built-in component library by adding your own custom React components. This allows you to create unique, interactive elements that match your documentation needs. Components are server-side rendered for better SEO and performance, with no layout shifts.

Defining a constant

Don’t use a React component to define a constant. Instead, consider using reusable snippets.

Custom components in MDX

1

Create a React component

Let’s start by creating a components folder where you can define your React components. Note that the React components can be defined in .ts, .tsx, .js or .mdx files.

components/CustomCard.tsx
1 export const CustomCard = ({ title, text, link, sparkle = false }) => {
2 return (
3 <a href={link} className="block p-6 rounded-lg border border-gray-200 hover:shadow-lg transition-shadow">
4 <h2 className="text-xl font-semibold mb-2">
5 {title} {sparkle && "✨"}
6 </h2>
7 <p className="text-gray-600">{text}</p>
8 </a>
9 );
10 };
2

Use the component in your docs

Once you’ve written the component, you can import it in your Markdown guides using either a relative path or the @/ prefix for an absolute path from your fern folder root:

guide.mdx
1// Absolute path from fern folder root
2import { CustomCard } from "@/components/CustomCard"
3
4// Or use a relative path
5import { CustomCard } from "../components/CustomCard"
6
7<CustomCard
8 title="MyTitle"
9 text="Hello"
10 href="https://github.com/fern-api/fern/tree/main/generators/python"
11/>

The @/ prefix resolves to the root of your fern folder, so @/components/CustomCard refers to fern/components/CustomCard. This is useful for nested MDX files where relative paths would be cumbersome (e.g., ../../../components/CustomCard). Both import styles are automatically transformed to relative paths at publish time.

3

Specify your components directory in docs.yml

Add your components directory to docs.yml so that the Fern CLI can scan your components directory and upload them to the server.

docs.yml
1experimental:
2 mdx-components:
3 - ./components

Why not just use custom CSS and JS instead?

While you can bundle React components as custom JavaScript, using Fern’s built-in React component support provides several key advantages:

When adding React components via custom JavaScript, you can’t control when components are rendered relative to the rest of the page content. This often leads to glitchy behavior where components flash or jump as they load asynchronously after the main content.

Custom JavaScript bundles typically include their own copy of the React library, which:

  • Increases page load time by duplicating React code that’s already included
  • Reduces performance as multiple React instances run on the same page
  • Creates larger bundle sizes that users have to download

Custom React components are server-side rendered and fully indexable by search engines, while components added via custom JavaScript aren’t server-side rendered and can’t be indexed.