# Docs platforms you keep

You keep your docs platform, whether it is Mintlify, GitBook, ReadMe, Docusaurus, Fern, Redocly, Astro, or a similar tool. EkLine works on the files it builds from.

## How EkLine changes your docs

EkLine works with docs that live as files in a Git repository, on GitHub or on gitlab.com.

1. You select the docs repository under **Where EkLine writes** in **Settings** > **Integrations** > **GitHub Integration** or **GitLab Integration**.
2. EkLine edits pages and sidebar files as plain files on a new branch.
3. EkLine opens a pull request on GitHub, or a merge request on GitLab.
4. Your team reviews and merges it.
5. Your platform builds and publishes the change, as it does for any other commit.

EkLine does not connect to a docs platform's API, editor, or dashboard. It never publishes your site.

EkLine looks for your framework's config file at the root of the repository. If it finds one, it follows that framework's rules for folders, file types, navigation, and components. If not, it treats the files as plain Markdown or MDX. Review each pull request as you would any other.

## What works on each platform

| Platform | What works today |
| --- | --- |
| **Mintlify** | EkLine edits the pages, the navigation file and other files in your repository, then opens a pull request. Mintlify publishes once you merge. EkLine does not use Mintlify's editor or API. |
| **GitBook** | Works through GitBook's Git Sync. EkLine edits the Markdown pages and `SUMMARY.md` in the synced repository, then opens a pull request. GitBook syncs the change once you merge. A space without Git Sync is not supported. EkLine does not use GitBook's API. |
| **ReadMe** | EkLine edits Markdown pages you keep in a Git repository, then opens a pull request. It does not run the `rdme` CLI or call ReadMe's API. It cannot edit pages that exist only in ReadMe's editor. To get a merged change into ReadMe, use the sync you already run, such as a CI job. |
| **Docusaurus** | EkLine edits Markdown and MDX pages and the sidebar file in your repository, then opens a pull request. |
| **Fern** | EkLine edits the pages and the navigation file in the `fern/` folder, then opens a pull request. Your usual Fern publish step picks up the change once you merge. |
| **Redocly** | EkLine edits Markdown and OpenAPI files as plain files, then opens a pull request. It has no special handling for Redocly, so check Redocly syntax when you review. |
| **Astro and Starlight** | EkLine edits Markdown and MDX pages and the sidebar in your Astro config, then opens a pull request. |
| **Potluck Docs** | EkLine edits Markdown and MDX pages and the sidebar in `src/config/sidebar.mjs`, then opens a pull request. The template generates llms.txt, Markdown pages, the sitemap and JSON-LD. |
| **MkDocs, VitePress, and others** | Any docs site built from Markdown or MDX files in Git works the same way. |

## Start a new docs site

[Potluck Docs](https://potluck.ekline.io) is EkLine's open source docs template, built on Astro and Starlight. EkLine works with it like any Astro site. These docs run on it.

## What you need

- A docs repository on GitHub, or a project on gitlab.com. See [Connect GitHub](/agent/github-app-setup/) or [Connect GitLab](/agent/gitlab-setup/).
- That repository chosen under **Where EkLine writes**. Until you select one, the GitHub Integration page shows **Setup is not finished: no documentation repositories chosen**.
- Your code repositories under **What else EkLine can read**, so EkLine can see what changed and why. It never writes to them.

If you do not see the **GitHub Integration** or **GitLab Integration** tab, contact support@ekline.io.

## Help centers and knowledge bases

Confluence and Pylon knowledge bases do not live in Git. EkLine updates them directly, after someone clicks **Update KB** in the editor. See [Manage a Confluence or Pylon knowledge base](/agent/manage-knowledge-base/). If you do not see the **KB Management** tab under **Settings** > **Integrations**, contact support@ekline.io.

For every tool EkLine connects to, see the [Integrations overview](/agent/integrations/).

## FAQ

### Does EkLine publish my docs site?

No. EkLine opens a pull request or merge request. Your site changes only after your team merges it and your platform builds it.

### Can EkLine edit docs that live only in GitBook's or ReadMe's web editor?

No. EkLine edits files in a Git repository. For GitBook, enable Git Sync. For ReadMe, keep your Markdown in Git and sync it to ReadMe with your own tools.

### Does EkLine work with self-managed GitLab or Bitbucket?

Not for editing your docs. EkLine edits docs and opens pull requests only on GitHub and gitlab.com. Self-managed GitLab and Bitbucket are not supported. To run Docs Reviewer checks in Bitbucket Pipelines, see the [Bitbucket integration guide](/reviewer/integrations/bitbucket-integration/).

### Can EkLine publish to Zendesk, Intercom, Webflow, or another CMS?

No. The **Zendesk** card in **Settings** > **Integrations** shows **Coming soon**. EkLine has no integration for Intercom, Webflow, or any other CMS.