What on earth do diagrams have to do with trust in docs? Docs that are useful, accurate, and up to date would increase trust.
Design structured diagrams, built to increase your team's trust in your docs
31–40 of 83 posts
Re: Design structured diagrams, built to increase your team's trust in your docs
#32What on earth do diagrams have to do with trust in docs? Docs that are useful, accurate, and up to date would increase trust.
We agree - useful, accurate, and up to date docs are what increases trust! We're bringing docs closer to the diagrams to visually explain your system in smaller chunks. We've found docs often accompany diagrams, and they become out of date as soon as they're exported! We think instead of diagrams being in docs, docs should be in the diagram.
Re: Design structured diagrams, built to increase your team's trust in your docs
#33I've always felt that these type of tools shouldn't have a traditional home page with sign up, sign in, etc. If you go to Excalidraw's website, it immediately launches the application for you to start using it. If you need extra features, only then you go to a page that provides details, pricing, etc. This is a beautiful pattern that makes these type of tools a daily habit for people to use. I don't want to create an…
I get that, but they want to collect your email to improve marketing. If the product is strong enough it may not matter. Practically speaking, I think getting user signup info is pretty important.
Re: Design structured diagrams, built to increase your team's trust in your docs
#34Is anyone using dot and/or graphviz in earnest for something like this?
PlantUML uses a declarative approach to diagrams and works well with dot and graphviz.
Re: Design structured diagrams, built to increase your team's trust in your docs
#35I have been using whimsical for diagrams and prototyping prototypes. Some of my colleagues are converted after they have seen it. The ease of use is the best I have seen so far. It is bold and easy to read.
Seeing the demo page, I have to ask: why do we stay with the traditional black, grey and white colors for diagrams?
Re: Design structured diagrams, built to increase your team's trust in your docs
#36Re: Design structured diagrams, built to increase your team's trust in your docs
#37What ever happened to the spirit of open source... Everyone trying to make a quick buck on some SaS scheme.
Re: Design structured diagrams, built to increase your team's trust in your docs
#38Any thoughts oh lucidchart : https://www.lucidchart.com/
Re: Design structured diagrams, built to increase your team's trust in your docs
#39Earlier quoted context omitted.
For diagrams that are long-lived and refactorable, diagrams-as-code is really your only option. Changing complex diagrams with drag-and-drop interfaces is a nightmare.
I wish there would be a mixture of diagrams.net and mermaid.
draw.io/diagrams.net has a mermaid plugin
Re: Design structured diagrams, built to increase your team's trust in your docs
#40Having fallen back in love with PlantUML recently I’ll never use a proprietary tool that doesn’t have declarative syntax. System diagrams and documentation are a crucial part of any software business and one that is regularly out of date as people end up using tools like draw.io which nobody knows how to get access to or use.
> I’ll never use a proprietary tool that doesn’t have declarative syntax
Can you provide an example of what you're referring to?