Replies: 2 comments 2 replies
-
yep, my feedback would be; don't use plantuml 😅 |
Beta Was this translation helpful? Give feedback.
1 reply
-
I think we should also support free graphing with tools such as drawio. Then find a way to annotate diagram parts so we can extract them technically. There are diagram types that are hard to make with as-code tooling. I've also heard of people doing architecture that are not so much into as-code. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The idea is to use Sphinx-Needs to model a Software Architecture and be able to
Use cases
Status quo
Sphinx-Needs
PlantUML
There are plenty of other Architecture-as-code solutions out there. But as Sphinx-Needs is already using PlanUML and generating PlantUML-specific code for a need, implementing C4 could be quite easy.
What's the difference to the existing "arch-support" in Sphinx-Needs?
The current implementation is quite open and allows any kind of representation and data interpretation.
The PlantUML-C4 model needs a strict syntax and has predefined elements and views. This makes it easy to use and write common docs.
What's the idea
needc4
directive, which is able to paint with the help of PlantUML-C4 the different views based on given needs/filters.I guess this all should be a new Sphinx extension, like Sphinx-Test-Report.
Any feedback on this idea? :)
Beta Was this translation helpful? Give feedback.
All reactions