# A docs site without a repo or a deploy

Documarium is a Docusaurus alternative for a public docs site with no repo, build or deploy to run: it is hosted, and you change it by asking Claude.

A static-site framework such as Docusaurus, MkDocs or Starlight, on a host like Cloudflare Pages, Netlify or Vercel, stays the better choice if you want to own the stack and keep the docs beside your code.

Prepared by Documarium. Framework and host facts come from their own docs, listed with the dates we read them under Sources.

## The short answer

It is not a question of skill: the question is whether you want to own it.

- **Choose a framework on your own host** if you want to own it: any design you can build, the docs next to your code, changes reviewed where your code is reviewed, and a bill that is your host's plan.
- **Choose Documarium** if you would rather have it handled. No install. No framework to learn. You ask Claude for a change in ordinary words, look at it first, then publish it.

## Two ways to run a docs site

Docusaurus, MkDocs and Starlight turn Markdown files into a website. Docusaurus's own docs say its job is to build your site into static files, and that hosting them is up to you. Cloudflare Pages, Netlify and Vercel can connect to your code on GitHub and build and deploy the site each time someone pushes a change. Full control, and someone on your side looks after it.

Documarium is the hosted way. There are no files to build and nothing to deploy: Claude reads and changes your pages through the Documarium connector, and Documarium stores, versions and publishes them.

## What you look after

| | A framework on your own host | Documarium |
|---|---|---|
| Where the docs live | Files in your code on GitHub or GitLab, which your host builds into a site | Hosted by Documarium. Your pages are not kept in your code, and you need no GitHub account to change them |
| How a change goes live | Someone changes the files and pushes them; the host builds and deploys the site. Cloudflare Pages and Vercel give each proposed change its own preview address | You ask Claude. Every change arrives as a proposed change with a preview link, nothing publishes until someone applies it, and then you ask Claude to publish |
| Framework updates | Yours to run. Docusaurus keeps upgrade guides for the breaking changes between major versions; Starlight asks you to update it regularly | No install. No framework to learn. |
| Look and design | Anything you can build, down to your own components | Your logo, small icon, main colour, typeface and one of four themes. There is no place for your own stylesheet and no theme editor |
| Undo | The history of your code, and on Cloudflare Pages a rollback to any earlier successful production build | Every version kept while the site exists; plans limit only how far back you can see and put back |
| Your own web address | Set up with your host | On Solo and up; Documarium handles the security certificate and renews it |
| Who can edit | Anyone with access to the code | Anyone you invite, each from their own Claude account; more than one editor needs Team or above |

## Asking Claude is not the difference

If you already ask Claude to change files in your code, it can change your docs files the same way. Asking in ordinary words does not set the two apart. What sets them apart is what sits around the docs: on your own stack you own the build, the framework, the theme and the hosting; on Documarium those are handled for you.

### If some of your editors don't work in code

On Team and above, the people you invite change published pages from their own Claude account, without access to your code. Documarium's whole job is letting people without repo access change published pages, safely and undoably.

## Where your own stack is ahead

- **Control.** Any framework, any design, your own components and your choice of host.
- **Docs next to the code.** A docs change can be reviewed with the code it describes, on GitHub or GitLab. Documarium does not keep your pages in your code.
- **Cost.** Your stack costs what your host charges. Publishing on Documarium needs a plan; plans are on the [Documarium pricing page](https://documarium.com/?utm_source=docs&utm_medium=organic&utm_campaign=C005&utm_content=PG-2026W44-007#pricing).
- **Teams without Claude.** Documarium has no single sign-on, and nothing for teams that do not use Claude.

## Taking your content out

The site's owner exports every page as plain text files in Markdown from **Export** in the sidebar, on every plan, including after you stop paying. You also get the page order, the look you chose and a list of every saved version. The export is your content, not a working website: to put it online somewhere else, you host it yourself, with a framework of your choice if you like. See [Download all your content](https://docs.documarium.com/guides/export/).

## Moving over

1. Open [documarium.com/start](https://documarium.com/start?utm_source=docs&utm_medium=organic&utm_campaign=C005&utm_content=PG-2026W44-007) and choose *Code repo*. Type the web address of your code on GitHub. Public repos work as-is; private ones need GitHub connected in Claude first. If your docs site is already online, you can choose *Docs online* and give its home page instead. Then choose which pages Claude writes.
2. [Add Documarium to Claude](https://docs.documarium.com/getting-started/installation/) and paste the prompt the start page gives you.
3. Claude reads your source, drafts the pages you chose and gives you a preview link to check before you keep it. It drafts new pages from what it reads rather than copying your site page for page, so check each one. You do not need an account for the preview. Anyone with the link can open the preview while it lasts; it isn't private.
4. To keep it as a draft, see [Keep a preview as a draft](https://docs.documarium.com/guides/keep-a-preview/). Write and preview your site for free, for as long as you like. To put it online, pick a plan and [publish](https://docs.documarium.com/guides/publish/). For your own address, from Solo, you add one record where you bought it; see [Use your own web address](https://docs.documarium.com/guides/custom-domain/).

## Sources and dates

1. Docusaurus, "Introduction", https://docusaurus.io/docs, read 2026-10-27.
2. Docusaurus, "Deployment", https://docusaurus.io/docs/deployment, read 2026-10-27.
3. Docusaurus, "Upgrading", https://docusaurus.io/docs/migration, read 2026-10-27.
4. MkDocs, https://www.mkdocs.org/, read 2026-10-27.
5. Starlight, "Getting Started", https://starlight.astro.build/getting-started/, read 2026-10-27.
6. Cloudflare Pages, "Git integration", https://developers.cloudflare.com/pages/configuration/git-integration/, read 2026-10-27.
7. Cloudflare Pages, "Preview deployments", https://developers.cloudflare.com/pages/configuration/preview-deployments/, read 2026-10-27.
8. Cloudflare Pages, "Rollbacks", https://developers.cloudflare.com/pages/configuration/rollbacks/, read 2026-10-27.
9. Netlify, "Create deploys", https://docs.netlify.com/deploy/create-deploys/, read 2026-10-27.
10. Vercel, "Deploying Git repositories with Vercel", https://vercel.com/docs/git, read 2026-10-27.
11. Documarium, [Create a site from what you have](https://docs.documarium.com/guides/create-a-site/), [Change a page and approve it](https://docs.documarium.com/guides/change-and-approve/), [Logo, colours and theme](https://docs.documarium.com/guides/branding/), [Use your own web address](https://docs.documarium.com/guides/custom-domain/) and [Download all your content](https://docs.documarium.com/guides/export/).
12. Documarium, [GitBook vs Mintlify vs Cloudflare Pages for small teams](https://docs.documarium.com/benchmarking/), facts checked 2026-10-16.

Documarium is an independent product. It is not made by or affiliated with Anthropic; Claude is a trademark of Anthropic, PBC.

Source: https://docs.documarium.com/benchmarking/docs-without-a-repo/ · Updated 2026-11-01