Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggested Improvements for Auto-Generated Views Pages #641

Closed
kristoflagae opened this issue Nov 26, 2024 · 1 comment · Fixed by #642
Closed

Suggested Improvements for Auto-Generated Views Pages #641

kristoflagae opened this issue Nov 26, 2024 · 1 comment · Fixed by #642

Comments

@kristoflagae
Copy link

I have a few suggestions to enhance the pages that list auto-generated views (context views, container views, etc.):

Improve Title Readability
For complex views with many elements, the title of the view can become hard to read.
It would be helpful to display the title as a subtitle on the page for better visibility.
(See orange arrows in the attached image.)

Preserve View Order from DSL File
Currently, views on pages with multiple views are not displayed in the order defined in the DSL file.
Instead, they seem to be ordered alphabetically by name.
Can the views be displayed in the same order as in the DSL file?

Clarify Links to Zoomed Views
Each diagram includes a link to a zoomed version, labeled with the system name and type (e.g., "system context," "containers").
When there’s only one view on a page, this is fine. However, on pages with multiple views, these links can become confusing.
Could the title of the view be used for these links instead? Or would another solution make more sense?
(See blue arrows in the attached image.)

image

@jenspav
Copy link
Collaborator

jenspav commented Nov 26, 2024

Are you able to give this a try: #642 ?

The rendering of the title in the diagrams itself is unfortunately out of our hands.

PS: You can also set diagrams and image descriptions in the model, those are also rendered in the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants