---
title: "SupportPages for Open Source: Public Repo Support"
canonical: https://supportpages.io/blog/supportpages-for-open-source-public-repos
updated: 2026-04-29
---

You can now point SupportPages at any public GitHub repository. No GitHub App to install, no permissions dance - paste the repo, get a help centre.

## Why this matters

Open-source projects have a documentation problem that's worse than SaaS's, not better. The code is often brilliant. The README is usually decent. But end-user documentation - the "how do I actually use this thing" layer for people who will never read the source - is chronically missing, because nobody's on the hook for it and the people capable of writing it would rather be writing code.

The irony is that open source is the *easiest* case for generated docs. The entire codebase is public. There's nothing to negotiate access to. The only thing missing was a tool that would read it and do the work.

## Proof, not promises

We've been using this internally for a while, and it's how our example help centres are built. The help centres for [WordPress](https://wordpress.supportpages.io), [Cal.com](https://cal.supportpages.io), [DocuSeal](https://docuseal.supportpages.io), and [Plausible](https://plausible.supportpages.io) were each generated from the project's public code - sections, articles, screenshots, all of it. No hand-written content, no insider knowledge, just the repository.

I keep these public because "AI writes your docs" is the kind of claim that deserves inspectable evidence. Click through them and judge the output yourself.

## Who this unlocks

- **Maintainers** who want end-user docs without burning contributor goodwill on doc chores
- **Companies building on open source** - if you run a hosted or forked version of an OSS tool, you can give your users a proper help centre for it
- **Anyone evaluating SupportPages** - try it on a public repo you know well before connecting anything private

That last one matters to me. The best way to judge whether SupportPages understands code is to watch it document a codebase where you already know where the bodies are buried.

Same rules as always: read-only, nothing stored, analysis runs in a throwaway sandbox. Public repos don't get looser handling just because the code is public.

We're onboarding design partners ahead of launch. Take a look at [supportpages.io](https://supportpages.io) and get in touch.

---

## About the Author

**Simon Moxon** has been building SaaS companies since 2009. He's scaled teams to 20+ people, hit £2m ARR, and learned most of the lessons the hard way. Now he's building [SupportPages.io](https://supportpages.io) - help docs that write themselves when you ship code. He writes about what's changed in SaaS and what hasn't.

[Twitter](https://twitter.com/simonmoxon) · [LinkedIn](https://www.linkedin.com/in/smoxon/)