Images not always resolvable, am I doing something wrong? #202
Unanswered
timothystone
asked this question in
Q&A
Replies: 2 comments 1 reply
-
|
If you'd like some assistance, please attach a ZIP file with an example. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I finally had some time to create something that wasn't proprietary... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Given the following directory layout:
I have an
!adrsand!docsin myworkspace.dslreferencing each.Neither the
adrsordocsdirectories can see theimages, i.e.,../images/image.pngis unresolvable, while the same is fine in GitHub/GitLab rendering.I could move the
imagesfolder toadrsanddocs. Doing so creates possible duplication and breaks the markdown in the browser.Something is amiss. How is this suppose to work across all possible views? It has something to do with how Structurizr is scoping the "Documentation" and "Decisions" view,
!docsand!adrsrespectively that theimagesfolder at the root is "lost" in the workspace context on launch.I could not find an answer in a "Closed" query and the FAQ is silent. Seems like it would be a common enough configuration question: Where should my common images lay for consistent rendering in Structurizr and GitHub/GitLab?
Beta Was this translation helpful? Give feedback.
All reactions