The official chat room for Antora is now located at https://antora.zulipchat.com. Please join us there!
Hello I try to generate plantuml
on the fly with antora
we have already production documentation where we used something like : plantuml::_images/_Usecase.puml[png]
I am not sure if this the way to go https://github.com/Mogztter/asciidoctor-kroki#antora-integration I try it to configure on in the site.yaml
but I get some JS
exeptions...
My configuration looks like :
site:
title: "Antora Docs"
url: https://marzelwidmer.github.io.
start_page: component-a::index
robots: allow
git:
ensure_git_suffix: false
content:
branches: master
sources:
# - url: https://github.com/marzelwidmer/antora-component-a.git
- url: ./../antora-component-a
ui:
bundle:
url: https://gitlab.com/antora/antora-ui-default/-/jobs/artifacts/master/raw/build/ui-bundle.zip?job=bundle-stable
snapshot: true
output_dir: ui-bundle
supplemental_files: ./supplemental-ui
output:
dir: ./public
asciidoc:
extensions:
- asciidoctor-kroki
However, in Antora, this is not currently compatible with inline SVG images.
get it correctly that this is not supported what I need...
I'm migrating my Maven-generated documentation to Antora, but there are a few things I have difficulty with, especially with diagrams/PlantUML. I can generate and fetch them, but I couldn't find how to:
asciidoc.attributes.plantuml-config
, but it seems not to work)Am I trying to do things that are not possible yet, or am I just going at it the wrong way? Thanks!
Hi all, we currently define our playbook as follows:
site:
title: Debezium Documentation
url: https://www.debezium.io/documentation
content:
sources:
- url: https://github.com/debezium/debezium.git
start_path: documentation
branches:
- '1.6'
- '1.7'
- 'master'
This obviously leads to master being published to /documentation/reference
and then having /documentation/reference/1.7
and /documentation/reference/1.6
.
I'm wondering if there is a way to change this behavior somewhat so that we would actually publish branch master to /documentation/reference/dev
and then publish branch 1.6 to /documentation/reference/stable
.
Can this be done in one playbook or would multiple playbooks be required for this?
site:
title: Docs
content:
sources:
- url: https://github.com/abyshukla/antora-sandbox.git
branches: [master, tinkerings]
ui:
bundle:
url:./../antora-ui/build/ui-bundle.zip