Referencing other diagrams

[mikeholczer]

Has there been any discussion about having the ability to break a larger diagram down into multiple diagrams and being able to then combined them together. I'm thinking about architecture diagrams mostly, where you might have a large system where different people own maintaining the documentation for various sections of it and/or where sub-systems are in different source control repositories and you want each parts diagram to live in the code repositories, but then still have an easy way to generate the complete diagram.

[muteboy]

If there was a way to embed content from other diagrams, that would be great. D2 can do this, and it's very useful, especially for defining classes and styles in one place and then importing/embedding them.

[mikeholczer]

Yeah, it was from looking at D2 that made me want to ask here, but it doesn't seem like D2 is under active development anymore and certainly doesn't have the adoption or community that mermaid does.

I was thinking for class diagrams and architecture diagrams for distributed systems, where you might want to have subparts of the diagrams be owned by different teams and/or be in different source control repos, but be able to create the full diagram when needed.

[OliverWilliamsDataManager]

Would find this a very useful thing indeed. Some of my diagrams are so complex they need to be be split and linked. It also would help to link together diagrams that deal with a higher and lower levels of detail.

[EmnaBarbouch]

This would be a great addition. A native include or import directive would make Mermaid much more practical for large teams and distributed systems. Definitely something worth pushing for.