-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[116] ADR: Use Mural for diagramming and whiteboarding #122
Conversation
This sounds great. We would use another tool for something like EDR diagramming or creating a network diagram but we can incorporate those as we go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tool selected and justification makes sense to me! Figjam/Figma does offer an architecture diagramming tool so that would reduce the need for another tool in the future, like @acouch mentioned. However, I don't think that outweighs existing knowledge and licenses. Is it worth considering that we may want to reconsider switching when the Mural licenses expire?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great to me! I'll approve so we're not blocked on merging, but would love for @itsemilyianacone or @lucasmbrown-usds to sign off as well.
The Pros and Cons list make it really easy to see why Mural is an obvious choice, and the positive and negative consequences are thoughtful and help inform some other decisions in the project. Excellent work overall!
|
||
### Negative Consequences <!-- OPTIONAL --> | ||
|
||
None, realy. There's a possible duplication of tool capabilities — Figma comes with Figjam, which has similar features; engineers may prefer MermaidJS for diagraming — which may justify further analysis in the future. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
### Positive Consequences <!-- OPTIONAL --> | ||
|
||
- Mural can be used for sprint retrospective board, eliminating the need for an retro-specific tool |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a helpful observation! We do have "Sprint Retro Tool" listed as one of the ADRs associated with the Comms Platforms milestone. Mural should at the very least be one of the options we consider, if not the one we select just to get things rolling this sprint.
|
||
## Decision Outcome <!-- REQUIRED --> | ||
|
||
Chosen option: Mural, because HHS has existing licenses and Nava has extensive experience using it for multiple purposes (diagrams, whiteboard, research synthesis, brainstorming, etc.). Mural is very effective as a collaborative drawing canvas. And it will be valuable to all disciplines for various purposes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since Figma comes with Figjam, and has similar features, and we plan to already use Figma, wouldn't it reduce mental surface area needed and complexity to stick with one tool rather than learning two? Both tools are almost the same but worth noting different navigation, which personally isn't desirable for me. It's context switching without a lot of benefit. For simplicity sake, I like Figma + Figjam. Just chiming in!
LGTM! |
@itsemilyianacone gave me a 👍 over chat on this, too |
Resolves #116
This PR proposes the use of Mural for diagramming and whiteboarding.
Thinking about this tool from a cross-discipline perspective. There's overlap with eng/product/project needs. @acouch, it'd be good to get engineering's opinion on the MermaidJS bits. @sumiat / @widal001, it's be good to get your product perspective.