It would be nice, if the asciidoctor-editor would be compatible with antora conventions/concepts (antora docs)
In particular, resolving of resources would be helpful, taking family directories into account.
E.g. instead of always working with relative paths like this
----
include::../examples/Test.properties[]
----
one would write
----
include::example$/Test.properties[]
----
where the "example" family is being used.
More complex scenarios are possible, see https://docs.antora.org/antora/latest/page/resource-id-coordinates/, but resolving component-local resources would already help a lot.
The intellij-plugin, as well as the vscode-plugin (partially) support this.
Here's a comment from @ahus1 about how to improve this step by step for the vscode-plugin:
asciidoctor/asciidoctor-vscode#434 (comment)
It would be nice, if the asciidoctor-editor would be compatible with antora conventions/concepts (antora docs)
In particular, resolving of resources would be helpful, taking family directories into account.
E.g. instead of always working with relative paths like this
one would write
where the "example" family is being used.
More complex scenarios are possible, see https://docs.antora.org/antora/latest/page/resource-id-coordinates/, but resolving component-local resources would already help a lot.
The intellij-plugin, as well as the vscode-plugin (partially) support this.
Here's a comment from @ahus1 about how to improve this step by step for the vscode-plugin:
asciidoctor/asciidoctor-vscode#434 (comment)