Publish internal documentation behind company SSO

Runbooks, architecture decision records, onboarding guides, process documentation – this content should be accessible to the whole company but not to the public internet.

The existing options:

• Confluence – $6.05–$11.55/user/month. Every reader is a paid seat. Requires Confluence's editor. Static doc builds don't import cleanly. Good for collaborative editing; overkill for read-only distribution.
• GitHub Pages (private) – requires Enterprise Cloud ($21/user/month) and GitHub accounts for every reader. PMs, operations, and HR don't have GitHub accounts.
• GitBook – $249/month for visitor auth. Built for public-facing docs. Visitor authentication is treated as an enterprise upgrade.
• Notion – no way to serve arbitrary HTML. Embedding docs requires rebuilding in Notion's editor.
• Vercel – SSO is $300/month. Requires a git project for every site.
• S3 + Cognito – engineering days to set up, ongoing maintenance.

display.dev: publish your MkDocs or Docusaurus build, get a company-gated URL. €49/month. No per-seat pricing.

display.dev doesn't edit your documentation. It publishes it.

For collaborative documentation that teams write and maintain together – Confluence, Notion, and GitBook are excellent. Use them for that.

display.dev is for the publishing step: when you have a built artifact (a static HTML site) and need it accessible to the company behind company auth. The two tools complement each other – write in Confluence, publish supplementary HTML artifacts in display.dev.

name: Publish Internal Docs
 
on:
  push:
    branches: [main]
 
jobs:
  docs:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
 
      - name: Install and build
        run: |
          pip install mkdocs mkdocs-material
          mkdocs build --site-dir ./site
 
      - name: Install display.dev CLI
        run: npm install -g @displaydev/cli
 
      - name: Publish docs
        run: |
          BASE_VERSION=$(dsp get "${{ vars.DISPLAY_ARTIFACT_ID }}" | jq -r .currentVersion)
          dsp publish ./site/ --id "${{ vars.DISPLAY_ARTIFACT_ID }}" --base-version "$BASE_VERSION"
        env:
          DISPLAYDEV_API_KEY: ${{ secrets.DISPLAYDEV_API_KEY }}

Every merge to main automatically updates the published documentation using the artifact ID stored in DISPLAY_ARTIFACT_ID.