Remote Content

Pull documentation from GitHub repositories or HTTP endpoints at build time.

Planned design

Remote content will let you pull MDX files from external sources — GitHub repositories, S3 buckets, or any HTTP endpoint — and include them in your Publier sidebar as if they were local files.

The planned configuration:

content:
  sources:
    - type: github
      repo: my-org/backend-service
      path: docs/
      branch: main
      label: Backend API

At build time, Publier fetches the remote files and writes them into a temporary local directory that the content pipeline reads normally. Remote content appears in the sidebar and search index alongside your local pages.

Planned source types

Source	Description
`github`	Fetch MDX files from a GitHub repo path via the GitHub API
`http`	Fetch a single MDX file or a JSON manifest of files from any URL
`s3`	Fetch from an S3 bucket prefix (AWS, R2, MinIO)

Use cases

Multi-repo docs — consolidate documentation scattered across many service repos into a single site.
Generated references — pull API reference pages generated during your CI pipeline.
Shared content — reuse installation or security guides maintained in a central repo across multiple product doc sites.

Workaround today

Use Astro’s content layer to write a custom loader that fetches remote content. Publier consumes the docs collection produced by the loader.

Questions or feedback on remote content? Email [email protected].