You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
In our documentation, we do have a series of common assets to multiple modules, for example the icons. Thus in a document, we may have images coming from multiple sources. We can easily cross-reference within antora but the asciidoc preview in VS does not seem to support this configuration.
Note: For preview, we currently configure the attribute imagesdir to "../images", which works fine for most of the images. But we miss these common assets.
In our case, simply supporting the standard antora infrastructure would be enough.
For example:
[x] Automatically set imagedir from standard antora infrastructure.
Site description: [ site.yml ]
Describe alternatives you've considered
We are beginners to the system and may have not seen alternatives, so any better suggestion is welcome.
Additional context
We have a similar issue with include files. We have a series of common variables that describe product names, zones of interface or reusable sentences.
include::zAll:page$_attributes.adoc[]
For the include, we may opt to use the relative path instead of the ref ID, which will be compatible for the two modes. We are afraid that doing the same for images will make the document reading more complex.
include::../../zAll/pages/_attributes.adoc[]
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
In our documentation, we do have a series of common assets to multiple modules, for example the icons. Thus in a document, we may have images coming from multiple sources. We can easily cross-reference within antora but the asciidoc preview in VS does not seem to support this configuration.
Note: For preview, we currently configure the attribute imagesdir to "../images", which works fine for most of the images. But we miss these common assets.
Describe the solution you'd like
Preview images to understand the coordinate of a resource, as described here: https://docs.antora.org/antora/2.3/page/resource-id/.
In our case, simply supporting the standard antora infrastructure would be enough.
For example:
Describe alternatives you've considered
We are beginners to the system and may have not seen alternatives, so any better suggestion is welcome.
Additional context
We have a similar issue with include files. We have a series of common variables that describe product names, zones of interface or reusable sentences.
include::zAll:page$_attributes.adoc[]
For the include, we may opt to use the relative path instead of the ref ID, which will be compatible for the two modes. We are afraid that doing the same for images will make the document reading more complex.
include::../../zAll/pages/_attributes.adoc[]
The text was updated successfully, but these errors were encountered: