Skip to content

docs: add antora as main documentation tool#1963

Draft
fewerner wants to merge 12 commits intomainfrom
felix/antora
Draft

docs: add antora as main documentation tool#1963
fewerner wants to merge 12 commits intomainfrom
felix/antora

Conversation

@fewerner
Copy link
Contributor

What's new in this PR


PR Submission Checklist for internal contributors
  • The PR Title
    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

fewerner added 12 commits March 20, 2026 10:15
`antora.yml` defines the local documentation project.

`antora-playbook.yml` defines all sources that contribute to the
documentation site. It is best practice to have this in a separate
repostiory as it configures the documentation without actually defining
the content. For the start we place it here.
Part of the configuration is the UI. We use the antora default UI for
now.

`ROOT` is the default module in antora. Every module can have `pages`,
`partials`, and `examples`.

Run `bunx antora antora-playbook.yml` to build the docs.
Under the hood it requires ruby and installing the gems.
`make antora` builds the antora documentation
`make antora-attachments` pulls in the api docs as static assets, kotlin
an ts for now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant