Global Configuration
Customize your documentation using the docs.yml file
Not all of the properties in docs.yml
are documented here. If you’d like to see all properties, please check out the
the raw schema
Top-level properties
Every Fern documentation website needs a docs.yml
file with the core configuration settings.
A string that is used as the tab bar title.
Learn more about the logo
configuration here.
Relative filepath to the favicon.
Configure the primaryAccent
and background
colors. Learn more about the colors
configuration
here.
An array of paths you want to configure to permanently redirect to another path. Learn more about the
redirects
configuration here.
Array of names and urls of links you want to include as a call to action. Learn more about the
navbar-links
configuration here.
Set a custom background image to be displayed behind every page. Learn more about the
background-image
configuration here.
Customize the fonts used in your documentation website. Learn more about the
typography
configuration here.
Customize the layout of your documentation website. Learn more about the
layout
configuration here.
Creates a landing page for your documentation website. Learn more about the
landing-page
configuration here.
Sets the default language displayed by code snippets in the API Reference.
Options include: typescript
, python
, java
, go
, ruby
, csharp
, curl
Instances configuration
An instance
is the backend of a distinct docs website. Each instance is published to a unique domain using the --instance
flag. It is most common to use instances to configure staging and production docs which publish to separate URLs.
The URL where your Fern documentation is deployed. Must contain the suffix docs.buildwithfern.com
The custom domain where your documentation is hosted. Learn more about setting up a custom domain here.
If edit-this-page
is set, Fern will add an “Edit this page” link to the bottom of each page that links to the given public GitHub repository.
Learn more about the edit-this-page
object here.
Colors configuration
The configured accent primary color for light and dark mode.
The configured background colors for light and dark mode.
The border color is used for the borders of cards and other elements.
If sidebarBackground
is set, the sidebar will also render a 1px border on the right side.
By default, the sidebar will render with a transparent background without a border.
If headerBackground
is set, the header will render with a solid background, with a 1px solid border on the bottom.
By default, the header will render with a transparent background, with a 1px faded border on the bottom.
The background color of cards and code blocks.
Logo configuration
Where clicking on the logo links you to.
Path to the image for the dark mode logo. You can exclude this if you don’t have dark mode enabled. SVG format is recommended.
Path to the image for the light mode logo. You can exclude this if you don’t have light mode enabled. SVG format is recommended.
Redirects configuration
The path that you want to redirect from.
The path that you want to redirect to.
Toggle between permanent and temporary redirect (default false
). When true, the status code is 308. When false the status code is 307.
NavBar links configuration
One of outlined
, minimal
, or filled
. This value controls the styling of the button.
The url once you click on the button. Example: https://buildwithfern.com/contact
Text inside the button.
When true
, the border radius of the button will be fully rounded.
The Font Awesome icon to be used in the button. This icon will appear to the left of the text content. Pro and Brand Icons from Font Awesome are supported.
The Font Awesome icon to be used in the button. This icon will appear to the right of the text content. Pro and Brand Icons from Font Awesome are supported.
By default, the rightIcon
for a filled
button is set to arrow-right
.
Background image configuration
Relative filepath to the light-mode background image.
Relative filepath to the dark-mode background image.
Typography configuration
Customize page and section titles. If not supplied, defaults to the body font.
Learn more about font configuration here.
Customize paragraph text and other body text.
Learn more about font configuration here.
Customize code blocks and inline code snippets.
Learn more about font configuration here.
Font configuration
The name of the font. Defaults to a generated name that will be used to reference your custom font in the eventually injected CSS.
Relative filepath to a variable font file. If the font file is not variable, use paths
instead.
Supported font file types are .woff
and woff2
.
A list of font files for particular weights. Each element in the list includes a path
, weight
, and style
property.
Layout configuration
Sets the height of the header. Defaults to 4rem
(64px
). Valid options are {number}rem
or {number}px
.
Sets the maximum width of the docs layout, including the sidebar and content. Defaults to 88rem
(1408px
).
Valid options are {number}rem
, {number}px
, or full
.
Sets the maximum width of the Markdown article content. Defaults to 44rem
(704px
).
Valid options are {number}rem
or {number}px
.
Sets the width of the sidebar in desktop mode. Defaults to 18rem
(288px
). Valid options are {number}rem
or {number}px
.
Sets the placement of the searchbar. Can be one of header
, sidebar
or header_tabs
(places the searchbar in the header but on the tabs row).
Defaults to sidebar
.
disable-header
is set to true.Set the placement of the tabs. Can be one of header
or sidebar
.
Defaults to sidebar
.
disable-header
is set to true.Set the alignment of the Markdown content. Can be one of center
or left
.
Defaults to center
.
If set to true, the header will not be rendered. Instead, the logo will be rendered as part of the sidebar, and a 1px border will separate the sidebar from the content.
GitHub configuration
Be sure the repository is set to public visibility.
The owner of the GitHub repository where you host your documentation.
The name of the GitHub repository where you host your documentation.
The branch of the repository you would like the GitHub editor to open a PR to. Default is main
.
Landing page configuration
The name of the landing page.
Relative filepath to the desired landing page Markdown file.
See VapiAI’s landing page live and the associated Markdown file.