Skip to main content
iHub uses Mintlify as the writing and publishing interface and a Git repository as the durable source for its Markdown content.

One hub, two contribution paths

Visual workflow

Non-technical and technical contributors can edit pages in Mintlify’s web editor. They can work on a feature branch, preview the result, and publish it as a pull request for review. Mintlify commits accepted visual changes to the connected repository.

Git workflow

Developers can create a branch, edit Markdown in an IDE, open a pull request, and merge it after review. Mintlify detects the repository change and updates the published hub. In both cases, changes are reviewed before they reach the primary branch and published iHub.

Content lifecycle

  1. Draft: A contributor works on a feature branch in Mintlify or Git.
  2. Review: A subject-matter reviewer checks accuracy and clarity.
  3. Merge: The approved change enters the primary branch.
  4. Publish: Mintlify deploys the updated internal site.
  5. Maintain: The named owner reviews the page by its review date.

Access

The repository should be private. The published site must require authenticated team access. See Roles and publishing workflow for the recommended permissions.