You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we're not against some "duplication" if each library introduces enough value (e.g. unique style, significant additions), most of the submissions have ton of overlap and similar visual style.
What about creating a single library on this topic that contains all the items? Or at merge the libraries that makes sense to merge them (I'm not up to speed with the specific domains).
The only comment I have is while existing library introduces a set of single elements which are just colored squares UI-wise, I'd like to have predefined composites like in #506.
We can have both the single elements and composites as separate libs, or together. Don't know what makes more sense.
But, I wanted to open this discussion for you guys to propose which items should be include and whether they all make sense to be together, or some are from different design methodologies.
I was thinking about it. Maybe we could try to merge them, and keep a list of authors.
And maybe we could have something like a "templates" category, where you could have all elements in a single item. That would allow users to import all at once (like in Agile retrospective tools).
We have a ton of library submissions on Domain Driven Design / Process modelling /
Existing library:
https://libraries.excalidraw.com/?theme=light&sort=default#tylerkron-event-storming
Open submissions:
#928
#770
#569
#506
#583
#632
...I'm sure there are more.
While we're not against some "duplication" if each library introduces enough value (e.g. unique style, significant additions), most of the submissions have ton of overlap and similar visual style.
What about creating a single library on this topic that contains all the items? Or at merge the libraries that makes sense to merge them (I'm not up to speed with the specific domains).
/cc @aleixmorgadas @storv @lxgreen @AlexZeitler @sebastiandedeyne
/cc @pclainchard
The text was updated successfully, but these errors were encountered: