-
Notifications
You must be signed in to change notification settings - Fork 52
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
Diagrams as code in Sphinx documentation #908
Comments
See the discussion that initiated this: #889 (comment) |
I guess we should avoid Mermaid-based solutions for now. Mermaid is a Node.js tool, and mxcubecore has no dependency on Node.js. Same for D2, which is a Golang tool. |
Very nice :). Mermaid seems a bit more capable than the other two. I had a look at PlantUML and that also looked pretty good so I would be happy with that. |
If there is a preference for Mermaid, we can go with that. The Node.js dependency might not be that big of an issue, I do not know. I had in mind that both Mermaid and PlantUML were using very similar notation -- implying that it would be easy-ish to switch from one to the other later on if needed -- but that does not seem to be the case after all now that I am looking at those a bit closer. |
Turns out there is no need for Node.js for Mermaid after all. At least not for HTML where the transformation from Mermaid code is made directly in the browser. So here is an attempt: #954 |
It could be nice to be able to have diagrams as code in the documentation.
The source code for the diagram itself would be stored as text/code inside the Markdown or ReStructuredText document within a directive.
Possible technical solutions:
The text was updated successfully, but these errors were encountered: