Closed astridu closed 3 years ago
@astridu This is a bit too abstract for me to implement. Can you demonstrate this with real properties that we can see in stage?
It's also a bit large for one ticket. Can you split this into one ticket for the new hierarchy and one for marking properties as being entered?
Does this help?
Yes, this is much easier to understand. Thanks for doing the extra work @astridu
Developers; It looks like this removes the btn-primary
class from the sidebar. When this happens, also remove it from resourceNav.scss
and remove $vanilla
from colors.scss
@astridu can you add what the top-level items in the left nav should look like if they don't expand? See this example using: https://stage.sinopia.io/editor/ld4p:RT:bf2:Monograph:Item:Un-nested
In this case, it would have have the expand/collapse control. Selected property would be bold, black. Other properties would be bold, blue. Black dot to the right to indicate if it's filled in.
@astridu I'm looking for a mockup that mixes in the expand controls with those that don't get expand controls. How should those be positioned when we have a mix of hierarchical and non-hierarchical?
Like this?
@astridu Yes, thank you.
Dot on the right indicates whether content has been entered for that fieldMoved to #3100If user clicks 'Save' and required fields are not entered, they will display in red to indicate they need to be filled in.Moved to #3122Is there any opportunity to save what the user has expanded/collapsed so the next time the resource is opened, the same properties are expanded/collapsed?Moved to #3084