Problem to Solve
It would be useful to have a way to export our graph to use it elsewhere.
For example - to write an article, blog post, documentation or any other paper. Our current visualization is good but not ideal for inserting its image into some documents.
Current Workaround
We can take a screenshot of TypeDB Studio visualization. With its current color schema it can be challenging to integrate the screenshot into some documents.
Proposed Solution
We add a separate button to export the graph from TypeDB Studio. The same graph we are seeing in Studio graph visualisation. Preferably with PlantUML as it will be usable without any additional programming. Many different documentation/design instruments support it as diagram as code solution.
Additional Information
In case of PlantUML the exact design of the graph will not be preserved.
The code contains information only on elements types, names and relations. It looks like this
@startuml
(*) -right-> "Instrument Bytecode"
-right-> "Run unit tests"
note top: Delegated to Test Framework
-right-> "Collect Coverage Metrics"
if "use metrics" then
--> [check] "Verify Coverage Reqs."
--> (*)
else
--> [cobertura] "Compile Coverage Report"
--> (*)
endif
@enduml
The result of this code will look something like this:

Other examples of PlantUML can be found here - http://real-world-plantuml.com/.
Problem to Solve
It would be useful to have a way to export our graph to use it elsewhere.
For example - to write an article, blog post, documentation or any other paper. Our current visualization is good but not ideal for inserting its image into some documents.
Current Workaround
We can take a screenshot of TypeDB Studio visualization. With its current color schema it can be challenging to integrate the screenshot into some documents.
Proposed Solution
We add a separate button to export the graph from TypeDB Studio. The same graph we are seeing in Studio graph visualisation. Preferably with PlantUML as it will be usable without any additional programming. Many different documentation/design instruments support it as diagram as code solution.
Additional Information
In case of PlantUML the exact design of the graph will not be preserved.
The code contains information only on elements types, names and relations. It looks like this
The result of this code will look something like this:

Other examples of PlantUML can be found here - http://real-world-plantuml.com/.