# Introducing the Fern Editor - Edit Developer Docs in the Browser, Powered by Git **Date:** 2025-11-06 **Author:** Sarah Bawabe **Source:** https://buildwithfern.com/post/fern-editor > The Fern Editor makes writing developer documentation accessible to everyone. Non-technical teammates can edit docs in the browser while developers keep Git-backed workflows for review and version control. --- _TL:DR; The Fern Editor makes writing documentation accessible to everyone —  non-technical teammates can now edit docs without touching Git, while developers keep the Git-based workflows they rely on._ _Edit instantly in the browser, with every change versioned and reviewable like code._ ## **Why we built the Fern Editor** Documentation is a team effort, but until now, only technical teammates could contribute easily. Even small edits required Git setup, local environments, or help from an engineer. The easier is it for anyone on your team to update your docs, the more likely it is that your docs will be up to date and accurate. Our goal is to make it easier to go from “edit” to “publish”. The Fern Editor feels as intuitive as Notion — but every edit still flows through the same Git-backed workflow developers trust. ## How the Fern Editor works ### **Edit like you’re in Notion** .custom-video { border-top-left-radius: var(--_borders---radius--small); border-top-right-radius: var(--_borders---radius--small); border-bottom-left-radius: var(--_borders---radius--small); border-bottom-right-radius: var(--_borders---radius--small); box-shadow: 0 0 0 .0625rem #0e3f7e0a, 0 .0625rem .0625rem -.003125rem #2a33450a, .1875rem .1875rem .1875rem -.09375rem #2a33460a, 0 .375rem .375rem -.1875rem #2a33460a, 0 .75rem .75rem -.375rem #0e3f7e0a, 0 1.5rem 1.5rem -.75rem #0e3f7e0a, .5rem .5rem 3.5625rem 0 var(--radix--gray--4); position: relative; } `} /> Jump in and start editing right on your docs site. Drag blocks, reorder sections, and type `/` to insert new elements — headings, lists, images, videos, callouts, cards, and more. When you select text, a floating toolbar appears for quick formatting — bold, italics, links — powered by [Tiptap](https://tiptap.dev/). What you see is what you publish. Every edit renders exactly as it will in production. Now your whole team can contribute to product updates, release notes, and API guides without learning Markdown or Git. ### **Dev Mode: Markdown when you need it** Dev Mode provides full Markdown control directly in the browser. Toggle it on to view and edit the raw Markdown side-by-side with a live preview. You get syntax highlighting, auto-formatting, and frontmatter editing — all powered by [Monaco](https://github.com/microsoft/monaco-editor), the code editor that powers VS Code. ### **Backed by Git** Every edit in the Fern Editor creates a draft pull request through the **Fern GitHub App**. Teammates don't need GitHub accounts or Git knowledge — the app handles it all behind the scenes. Developers can review diffs, leave comments, and merge like any other PR. > Note: Support for **GitLab** and **Bitbucket** is coming soon, bringing the same docs-as-code workflow to any Git provider. ## **Try the Fern Editor today** Developer-friendly docs, editable in the browser, and still docs-as-code. [Bring your whole team into the doc-writing process.](https://dashboard.buildwithfern.com/) ### FAQs .faq-item { cursor: pointer; } .faq-header { display: flex; align-items: center; gap: 12px; } .faq-chevron { transition: transform 0.3s ease; flex-shrink: 0; width: fit-content; margin-top: 0.5rem; } .faq-item.open .faq-chevron { transform: rotate(90deg); } .faq-answer { display: none; } .faq-item.open .faq-answer { display: block; }

What is the Fern Editor in a nutshell?

The Fern Editor is a browser-based editor for your developer docs that feels like Notion but runs on your existing docs-as-code workflow. We built it after hearing that non-technical teammates found it intimidating to install a CLI, write Markdown, or learn Git commands.

Now, anyone can make visual edits in the browser — while developers keep full version control through pull requests.

Who can use the Fern Editor?

Anyone who contributes to documentation — from marketing, product, and support teams to technical writers and developers. In the future, we plan to let visitors to your documentation make suggestions through the Fern Editor too.

Do I need GitHub access to use it? Are other Git providers supported?

No. The Fern GitHub App manages commits and pull requests automatically — no local Git setup or GitHub account required.

While only GitHub is supported today, you can subscribe to this GitHub Issue as we build support for GitLab and Bitbucket.

How are edits reviewed and merged?

Every edit opens a draft pull request in your repository. Developers can review diffs, leave comments, and merge changes just like any other PR. Fern never pushes edits directly to production without review.

Can I edit Markdown or MDX components in the Fern Editor?

Yes. Toggle Dev Mode to edit Markdown or MDX inline with a live preview, complete with syntax highlighting and auto-formatting.

Can I edit docs.yml, custom CSS, or global JavaScript in Fern Editor?

No, not yet. Subscribe to this GitHub Issue as we build support for editing your entire docs configuration via the Fern Editor instead of having to go into YAML files.

Can I edit my API reference in the Fern Editor?

In Dev Mode we'll show you your OpenAPI spec. Any changes will apply to your OpenAPI Overrides file. Subscribe to this GitHub Issue as we build support for editing the API reference via the Fern Editor.

What's the price to use the Fern Editor?

Using the Fern Editor is included in all of our plans. We don't price per seat and encourage you to invite your whole team to contribute to your docs.

`} />