Organization GitHub configuration

The organization does not use personal member repositories for org-wide GitHub configuration. Two org-owned repositories hold that role.

Public vs private

Audience Repository Holds

Public repos

.github

Profile README, public workflow starter templates, canonical brand assets

Private repos

.github-private

Private workflow starter templates; mirrored brand assets

Upload the org avatar from .github/assets/logo-256.png (Organization settings → Profile). Keep .github-private/assets/ in sync when the mark changes.

What not to create

  • A personal antora-supplemental-private (or similar) under a member account for org health files or workflow templates — use .github-private instead.

  • A personal GitHub fork of Antora’s GitLab Default UI solely to host Antora upstream work — contribute via a GitLab fork of antora/antora-ui-default.

Related product names (themes)

The former monolithic package antora-dark-theme was split and renamed:

Personal forks of the old name are obsolete; use the org repositories above. See Theme products, Antora Dark Mode, and the Valentus installation guide on GitHub Pages.

Organization rename (history)

The GitHub organization was renamed from asciidoc-supplemental to antora-supplemental. URLs, playbooks, package metadata, and remotes were updated to match. Local clones should live under …/github.com/antora-supplemental/ (not the old org folder name).

See also