Closed simonbrowndotje closed 1 year ago
I had just started using the HTML export, but my use case may not be worth adding the feature back in for. I'm having trouble getting my organization to stand up an on-prem instance that's accessible to everyone (especially external organizations) and am not permitted to use the cloud version. So, I've essentially been exporting via the HTML method to share with other organizations. This method is convenient since it still has navigation functionality available.
There's a basic example of how to create your own offline diagram page, with double-click navigation, at https://github.com/structurizr/ui/blob/main/examples/diagram-navigate.html ... to be honest though, I'd just distribute the workspace.json
file along with a script to start the Docker build of Structurizr Lite. This way you have everything running locally, with the benefit of the full interactive diagrams.
Thanks for the tip @simonbrowndotje, we actually have been taking that approach internally (script + workspace.json
distribution via git repo). I think if our workspaces were scoped a little better, we could probably take the same approach with external as well.
The HTML and interactive SVG exports are less useful now that the diagram renderer can be used standalone ... leave a comment if you miss these features.