-
Design
-
Resolution: Done
-
Normal
-
None
-
None
Placing "relationships" in the redesign can be done in two ways:
1. We add relationships according to context. Say, for example in the "Add event" page the venue makes sense with time and date.
Pros
it goes with the flow in which we think about an event. It is morAll related information is chunked, not being asked randomly.
Sample Mockup for this
Cons
We will need to design this for every "Add xyz" page.
2. We have a relationship editor tab like we have now. With some default settings.
*Pros of this: *
All relationships in one box. Not a big change from how it is now. Same relationship editor can be used everywhere with defaults changed.
Our editors are already used to of this flow.
Cons
Well, not much really..except some information isn't placed where it is more related.
Sample Mockup for this
Feedback required on: Which option should we prefer, 1 or 2?
- is related to
-
MBS-9518 Default relationship types for entities
- Open