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
Hi, I just started using mermaid for our documentation using mkdocs recently and I am loving it. But one of issues that keeps me from using it to document large workflow diagrams that don't fit in a single page view is the lack of ability to pan and zoom, like the one you have with mermaid live editor
I searched through the issues/discussions and don't see any way to do this, so raising this issue. Hopefully we get enough support for this to make it a priority. Meanwhile I will take a shot at implementing it myself and submit a PR.
But please let me know if there a way to get this already. Thanks!
The text was updated successfully, but these errors were encountered:
I am aware of that problem. The reason why it is not solved yet, is that it is a question that involves several components of the MkDocs ecosystem.
Mkdocs-Mermaid2 is essentially Python, though there are Javascript and css parts in it. Those were generally contributed by others.
I am putting in copy the maintainers of Mermaid's live editor (@sidharthv96 and @knsv). Who knows, they might have some ideas, or suggest someone who could help?
Just in case, I am also putting the maintainer of the Material theme in the loop (@squidfunk) as the subject might interest him.
I am not sure that Mkdocs-Mermaid2 is the exact place where the problem should be solved, but perhaps a multilateral discussion could lead us somewhere?
Hi, I just started using mermaid for our documentation using mkdocs recently and I am loving it. But one of issues that keeps me from using it to document large workflow diagrams that don't fit in a single page view is the lack of ability to pan and zoom, like the one you have with mermaid live editor
I searched through the issues/discussions and don't see any way to do this, so raising this issue. Hopefully we get enough support for this to make it a priority. Meanwhile I will take a shot at implementing it myself and submit a PR.
But please let me know if there a way to get this already. Thanks!
The text was updated successfully, but these errors were encountered: