Item — HN Reader

May I ask a question? Why do you have to draw a sequence diagram with draw.io?

This response below is not going to answer your question.

Previously, I was using draw.io to draw sequence diagrams. I didn't have "fancy" setup. It was pretty straightforward. I drew diagram components, like actor, boundary, control, message, and lifeline and connected them one by one. This took so much effort and time. Then, I moved on and used PlantUML [0]. This tool helped me to produce a sequence diagram using text. The text will be rendered into a diagram. I didn't need to draw. It saved my time a lot.

[0]: https://plantuml.com/sequence-diagram

I like plantuml as well. I use it with all my preferences saved in vscode's user snippets. draw.io is seems to be preferred option at work as draw.io diagrams can be embedded into documentation (e.g., confluence) and are editable in future.

Ah, got it.

Actually, PlantUML is available as a plugin on Confluence. I am currently using the plugin at work. Since PlantUML supports converting a diagram to a SVG file, it should be embedable with other platforms too.

The good thing about PlantUML is that it's a text-based diagram tool. You can put the text in version control, like Git so you will know the revision history.