Sources
What Doc Holiday reads and writes: connection roles, freshness, and health.
What a Source is
Doc Holiday treats a Source as a connected system that contributes content or receives notifications. A Source can be a repository that Doc Holiday reads and writes, a context system it only reads, or the Slack Channel that carries notifications.
Other Sources stay read only and feed background material into Doc Holiday. Notion, Confluence, Linear, Google Drive, AWS (S3), and Azure Blob Storage all fit that shape when a team needs context instead of a writable destination.
Doc Holiday uses that mix of Sources in one workflow. A Publication points at one Source for the docs destination and at other Sources for context, so the same page can describe writable Sources and read only Sources without treating them as separate ideas.
That single model helps people who keep product notes in one place, source content in another, and the publication destination somewhere else. Doc Holiday can read across those places without making the reader learn three different kinds of connection logic.
For the shared vocabulary behind this page, see Concepts.
Provider connections and child Sources
Some Sources come in pairs. A provider holds shared access once, then Doc Holiday reuses that access for each individual repository or project underneath it. The UI shows provider labels and Source labels separately, so the shared Source stays distinct from the child Source it powers.
That split keeps workspace access in one place. It also lets a team add or remove individual repositories, projects, or channels without setting up the parent Source again or changing the rest of the workspace.
The parent provider usually holds the shared workspace or app access, while the child Source keeps its own name and settings. The child inherits the access it needs from the provider, which gives Doc Holiday a clean boundary between shared permissions and individual content Sources.
The pattern is the same across the supported providers:
GitHub Application provides access for GitHub Repository Sources.
GitLab Access Token provides access for GitLab Project Sources.
Bitbucket Workspace Access Token provides access for Bitbucket Project Sources.
Atlassian Application provides access for Jira Project Sources.
Slack Application provides access for Slack Channel Sources.
The same structure appears wherever Doc Holiday needs one shared permission set and many child Sources.
The pattern also keeps the setup story easy to follow. Once the provider exists, the child Source only needs the fields that belong to that specific repository, project, or channel, which keeps repeated setup work to a minimum.
Freshness and health
Doc Holiday rereads connected Sources on a background cadence, roughly every couple of hours for each Source. That keeps it close to the current state of the connected systems without waiting for manual refreshes.
Every Source also shows a health state. Healthy means Doc Holiday can use the Source. Unhealthy means Doc Holiday stops re-reading that Source until someone fixes the problem, so its information goes stale rather than fresh. If a Source stays unhealthy, the next draft can still use the healthy Sources, but the missing Source will not contribute until it recovers.
The health badge gives a quick answer to a simple question: can Doc Holiday trust this Source right now? If the answer changes, Doc Holiday stops re-reading that Source until the health problem clears. That keeps drafts from mixing current content with stale or inaccessible material.
For the operational details around credentials, health, and deletion, see Manage connections.
That page covers the day to day maintenance work, while this page stays with the idea of what health means and why Doc Holiday skips an unhealthy Source instead of guessing.
External Documentation
External Documentation connects Doc Holiday to an existing hosted docs site by URL. It reads that site as context and nothing more. Optional username and password fields support protected sites, which lets Doc Holiday reach material that sits behind a login.
That makes External Documentation useful when product notes, policies, or design references live in another system. Doc Holiday can read those pages alongside code and repository history without turning that external site into a publishing target.
This Source never publishes content back to the remote site, so it works as a read only reference rather than another docs destination.
If a team already keeps docs context in a managed site, External Documentation lets Doc Holiday read that material without copying it into another system first.
Set up a Source
When a team needs to add a new Source, the provider page shows the fields, validation, and workspace selection specific to that system. These pages cover setup, so this list stays short.
Last updated
Was this helpful?