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.
GitHub-Markdown (or GitLab-Markdown) supports relative links. Therefore it is possible to include, within a document with path //documentation/1.Introduction.md, an image belonging to a "sister" folder, e.g. //visualizations/BuildingBlocks.png.
Widoco does not support that, which forces us to use the full (absolute) path https://git.rwth-aachen.de/nfdi4ing/metadata4ing/metadata4ing/-/blob/develop/visualizations/BuildingBlocks.svg to include an image fom a different folder.
The disadvantage is that the full path contains also the branch. Therefore, if we have more branches at different maturity stages, the documentation for all branches will include always images from one branch, may it be the latest or the earliest, which often creates anachronysms.
Is there a solution for that?
The text was updated successfully, but these errors were encountered:
One option is to create multiple releases, using the direct links to the corresponding file.
The HTML just renders markdown, so if something is supported in markdown it should work too. That said, the sections are loaded dynamically, so I'd use the uniteSections flag
Is your feature request related to a problem? Please describe.
GitHub-Markdown (or GitLab-Markdown) supports relative links. Therefore it is possible to include, within a document with path
//documentation/1.Introduction.md
, an image belonging to a "sister" folder, e.g.//visualizations/BuildingBlocks.png
.Widoco does not support that, which forces us to use the full (absolute) path
https://git.rwth-aachen.de/nfdi4ing/metadata4ing/metadata4ing/-/blob/develop/visualizations/BuildingBlocks.svg
to include an image fom a different folder.The disadvantage is that the full path contains also the branch. Therefore, if we have more branches at different maturity stages, the documentation for all branches will include always images from one branch, may it be the latest or the earliest, which often creates anachronysms.
Is there a solution for that?
The text was updated successfully, but these errors were encountered: