# Docs Ahoy documentation

Docs Ahoy hosts documentation. You write pages in Markdown, organise them into folders inside **libraries**, and publish each library on your team's own address or on your own domain. Readers get fast, server-rendered pages; search engines and AI assistants get clean, machine-readable copies.

These pages are themselves written and published with Docs Ahoy.

## Where to start

:::page-ref
[Getting started](https://docsahoy.docsahoy.eu/docs/getting-started)
:::

:::page-ref
[Import from GitBook](https://docsahoy.docsahoy.eu/docs/import-from-gitbook)
:::

:::page-ref
[Writing](https://docsahoy.docsahoy.eu/docs/writing)
:::

## The words we use

| Word | What it means |
| --- | --- |
| Team | Your organisation in Docs Ahoy. It owns everything: libraries, images and files, people. |
| Library | A collection of pages that is published together, with its own address. GitBook calls this a space. |
| Page | One page in one language. |
| Document | A page together with all its translations. Plans count documents, so a page and its translations count once. |
| Change request | A named set of draft edits. Nothing is live until the change request is merged. |
| Asset | An image or file uploaded to your team, usable on any page of any library. |

## Two addresses

You work in the app at `https://app.docsahoy.com`. Your published libraries live on a separate domain, at `https://your-team.docsahoy.eu`, or on your own domain. Keeping published content on its own domain means one team's site can never affect another team's, or the app.