dispute-protocol/builder-prototype
2
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

Modules Library # of Modules #4

New Issue
Closed
opened 2025-04-21 05:13:59 +00:00 by sierrarod7 · 3 comments
sierrarod7 commented 2025-04-21 05:13:59 +00:00
Copy Link

Having 81 modules is WAY too many IMO and would be very overwhelming for a user. I would say 15 to 20 should be the max, especially considering if you are not familiar with conflict resolution, they may not know what some of these modules mean without further reading.

Having 81 modules is WAY too many IMO and would be very overwhelming for a user. I would say 15 to 20 should be the max, especially considering if you are not familiar with conflict resolution, they may not know what some of these modules mean without further reading.
Screenshot 2025-04-20 at 11.09.26 PM.png
325 KiB
Screenshot 2025-04-20 at 11.09.26 PM.png
ntnsndr commented 2025-04-21 18:44:51 +00:00
Owner
Copy Link

Thanks for this. I'm not sure I agree on this point, though.

The Modules Library may not actually be a necessary part of the interface; I mostly created it to make it easier for me to see what's in there. We might remove it before going public.

Currently, in the Builder interface, there are just a handful of Templates that are visible to the user. Templates are groupings of Modules. And Modules themselves are visible only on their relevant Component (i.e., question).

So for the primary user experience, users would not encounter more than a few modules at a time. And 15-20 modules is too few given the number of components in the system.

Can you reassess this issue in the context of the Builder interface rather than the Library?

Thanks for this. I'm not sure I agree on this point, though. The Modules Library may not actually be a necessary part of the interface; I mostly created it to make it easier for me to see what's in there. We might remove it before going public. Currently, in the Builder interface, there are just a handful of Templates that are visible to the user. Templates are groupings of Modules. And Modules themselves are visible only on their relevant Component (i.e., question). So for the primary user experience, users would not encounter more than a few modules at a time. And 15-20 modules is too few given the number of components in the system. Can you reassess this issue in the context of the Builder interface rather than the Library?
ntnsndr commented 2025-04-24 15:56:07 +00:00
Owner
Copy Link

One potential solution: Add a message to the top of the Library page making clear that this is for reference only.

One potential solution: Add a message to the top of the Library page making clear that this is for reference only.
ntnsndr commented 2025-05-08 04:22:12 +00:00
Owner
Copy Link

Module library no longer necessary, removed it: 41aeffa81b

Module library no longer necessary, removed it: https://git.medlab.host/dispute-protocol/builder-prototype/commit/41aeffa81bae959f202ccc23e2a1dc46babdac35
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dorohoward ntnsndr
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dispute-protocol/builder-prototype#4
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?