ARTEMIS-6111 migrate doc build to Antora

AGENTS.md

@@ -109,7 +109,7 @@ Required steps:
 
 ## Security Model
 
-**Authoritative Reference**: See [docs/user-manual/threat-model.adoc](docs/user-manual/threat-model.adoc) for the complete threat model including trust boundaries, adversary model, security properties provided/not provided, and triage dispositions.
+**Authoritative Reference**: See [our threat model](docs/user-manual/modules/ROOT/pages/threat-model.adoc) for the complete threat model including trust boundaries, adversary model, security properties provided/not provided, and triage dispositions.
 
 ### Security Review Checklist
 When reviewing code changes:

SECURITY.md

@@ -6,7 +6,7 @@ Artemis is a project of the [Apache Software Foundation](https://apache.org) and
 
 Before reporting a vulnerability please ensure:
 
-- It falls within the scope of our [threat model](docs/user-manual/threat-model.adoc).
+- It falls within the scope of our [threat model](docs/user-manual/modules/ROOT/pages/threat-model.adoc).
 - It has not already been reported. Existing advisories are enumerated on [our website](https://artemis.apache.org/components/artemis/security).
 
 To report a new vulnerability please follow the [ASF vulnerability reporting process](https://security.apache.org/report/).

artemis-website/docs-playbook.yml

@@ -0,0 +1,34 @@
+site:
+  title: Apache Artemis
+  url: https://artemis.apache.org
+  start_page: user-manual::index.adoc
+content:
+  sources:
+    - url: ..
+      branches: [HEAD]
+      start_path: docs/user-manual
+    - url: ..
+      branches: [HEAD]
+      start_path: docs/hacking-guide
+    - url: ..
+      branches: [HEAD]
+      start_path: docs/migration-guide
+ui:
+  bundle:
+    url: https://github.com/jbertram/artemis-antora-ui/releases/download/0.1/ui-bundle.zip
+antora:
+  extensions:
+    - require: '@antora/lunr-extension'
+      index_latest_only: true
+      index_by_heading: true
+asciidoc:
+  attributes:
+    sectnums: ''
+    project-name-full: Apache Artemis
+    project-name-full-url: apache-artemis
+    project-name-short: Artemis
+    project-version: ${project-version}
+    log4j-version: ${log4j-version}
+    artemis-console-version: ${artemis-console-version}
+output:
+  dir: target/site

docs/hacking-guide/antora.yml

@@ -0,0 +1,6 @@
+name: hacking-guide
+title: Hacking Guide
+version: ~ # version is essentially ignored since we always just deploy the latest
+start_page: ROOT:index.adoc
+nav:
+  - modules/ROOT/nav.adoc

docs/hacking-guide/modules/ROOT/nav.adoc

@@ -0,0 +1,8 @@
+* xref:code.adoc[Code Conventions]
+* xref:building.adoc[Building]
+* xref:tests.adoc[Tests]
+* xref:code-coverage-report.adoc[Code Coverage Report]
+* xref:validating-releases.adoc[Validating Releases]
+* xref:maintainers.adoc[Maintainers]
+* xref:history.adoc[History]
+* xref:notice.adoc[Legal Notice]

docs/hacking-guide/_building.adoc → docs/hacking-guide/modules/ROOT/pages/building.adoc

@@ -41,10 +41,8 @@ From the `artemis-website` module run:
 ----
 $ mvn -Prelease package
 ----
-This will build the user manual (both HTML & PDF), migration guide, hacking guide, & JavaDocs.
-Output will be placed in the `target/classes/user-manual`, `target/classes/migration-guide`, `target/classes/hacking-guide`, and `target/apidocs` directories respectively.
-
-Generating the user manual's PDF adds almost a minute to the build so this can be skipped using `-DskipWebsitePdfGeneration`.
+This will build the JavaDoc, user manual, migration guide, & hacking guide.
+JavaDoc output will be placed in the `target/apidocs` directory and the rest will be put into the `target/site` directory.
 
 == Offline
 

docs/hacking-guide/modules/ROOT/pages/index.adoc

@@ -0,0 +1 @@
+This hacking guide outlines how developers can get involved in contributing to the {project-name-full} project.

docs/hacking-guide/_maintainers.adoc → docs/hacking-guide/modules/ROOT/pages/maintainers.adoc

@@ -28,7 +28,7 @@ $ mvn -Pdev install
 ----
 == Commit Messages
 
-Please ensure the commit messages follow the 50/72 format as described xref:_code.adoc#commitMessageDetails[here].
+Please ensure the commit messages follow the 50/72 format as described xref:code.adoc#commitMessageDetails[here].
 This format follows the recommendation from the https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project[official Git book].
 
 == Configuring Git repositories

docs/migration-guide/antora.yml

@@ -0,0 +1,6 @@
+name: migration-guide
+title: Migration Guide
+version: ~ # version is essentially ignored since we always just deploy the latest
+start_page: ROOT:index.adoc
+nav:
+  - modules/ROOT/nav.adoc

docs/migration-guide/modules/ROOT/nav.adoc

@@ -0,0 +1,11 @@
+* xref:preface.adoc[Preface]
+* xref:key-differences.adoc[Key Differences]
+* xref:configuration.adoc[Configuration]
+* xref:connectors.adoc[Connectors]
+* xref:destinations.adoc[Destinations]
+* xref:virtual-topics.adoc[Virtual Topics]
+* xref:authentication.adoc[Authentication]
+* xref:authorization.adoc[Authorization]
+* xref:ssl.adoc[SSL]
+* xref:message-store.adoc[Message Store]
+* xref:notice.adoc[Legal Notice]

docs/migration-guide/_destinations.adoc → docs/migration-guide/modules/ROOT/pages/destinations.adoc

@@ -1,6 +1,6 @@
 = Destinations
 
-We already talked about addressing differences between ActiveMQ and {project-name-short} in the xref:README.adoc[introduction].
+We already talked about addressing differences between ActiveMQ and {project-name-short} in the xref:preface.adoc[preface].
 Now let's dig into the details and see how to configure JMS queues and topics.
 It's important to note here that both brokers are configured by default to _auto-create_ destinations requested by clients, which is preferred behavior for many use cases.
 This is configured using authorization security policies, so we will cover this topic in the later sections of this manual.

docs/migration-guide/modules/ROOT/pages/index.adoc

@@ -0,0 +1 @@
+This guide outlines how users can migrate an existing ActiveMQ broker installation to {project-name-short}.