Host your docs on docolin
docolin reads your docs straight from a public GitHub or Codeberg repo and keeps them in sync. Pick the path that fits you, from never-made-a-repo to already-fluent.
Host your docs on docolin
docolin reads your docs straight from a public git repo, on GitHub or Codeberg, and keeps them in sync. Point it at your repo once, and docolin takes it from there.
Pango writes his guides as Markdown in a git repo, the way you already do, and docolin reads straight from it, no separate CMS to learn, no copy-paste. It syncs that repo and turns each file into a doco: searchable, versioned, and open to verification and discussion.
The tutorial walks you from zero to a published, verified, AI-readable doco, end to end. This page is the hosting reference; the tutorial is the path.
What's here
This section is the reference. New to all this? Do the tutorial first, it walks you from zero, then come back here for the details.
The fast path if you already know git: point docolin at your repo and set the docs folder.
Polling, versions, what becomes a doco, and what happens when you delete one.
How it's organized: accounts own orgs, orgs hold projects, projects hold your docos.
The project page: sync status, fixing files that didn't publish, renaming, deleting.
The one requirement
Your repo must be public. docolin content is public by design and there's no private-repo sign-in flow, so a public GitHub or Codeberg repo is all you need. Everything else (an account, an org to hold the project) you set up along the way.
How it fits together
Your docs live in your repo. A docolin project points at that repo, and optionally a subfolder like docs/, inside an org you own. docolin handles the rest: an initial sync when you create the project, then it keeps up with your changes. The full model is in accounts, orgs, and projects.
Did this work on your setup?
Not rated yet