Hi everyone,
Static-site publishing and generated documentation come up regularly here—most recently in the discussion about self-hosting auto-generated pages
( Self-host auto generated pages ), and in the ongoing question of a Gitea Pages equivalent
( Publish static webcontent ).
I’m making Docs Portal public: a self-hosted companion application that turns documentation stored across Git repositories into one authenticated static documentation site.
It is built for teams that keep Markdown beside their code, infrastructure, and operational repositories, but want a single place to browse the rendered result.
What it provides:
- Syncs one or more Git repositories and selected documentation directories
- Builds a unified static site with MkDocs Material
- Uses push webhooks for fast rebuilds, with polling as a fallback
- Keeps the last successful static site online if a build fails
- Supports project isolation, Admin/Viewer roles, build logs, and build history
- Runs with Docker Compose and works well alongside a self-hosted Gitea instance
The focus is documentation/static sites rather than replacing Gitea or becoming a general-purpose hosting platform. Gitea remains the source of truth for Git; Docs Portal handles
aggregation, rendering, and publishing.
Repository and screenshots:
I’d be very interested in feedback from people currently using Gitea Actions, custom web-server deployments, or manual workflows to publish MkDocs, Jekyll, Hugo, or other
generated documentation.
