-
Notifications
You must be signed in to change notification settings - Fork 80
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
Collections Page: Collections Sidebar #1089
Comments
@jmakowski1123 @lizc577 @sdaitzman @marcotuts This is ready for AC testing on the sandbox |
@sdaitzman What was the original set of requirements behind the Collection Stats: Content Type counts? I can't seem to find the designs for that bit, and I don't remember discussing the specs. It currently seems to be configured such that the three most recently added content types get a slot, and anything else gets lumped under "other". I'm thinking instead, the three persistent slots should be problem, text and video, and everything else gets lumped under other. What are your thoughts? |
A minor correction: the three types with the highest count get a slot. We use alphabetical order as second criteria. In this example, we have "Text" before "Problem" because "Text" is actually "html". We also can change it if you think there is a better way. |
@jmakowski1123 @rpenido I agree that those three persistent slots should be problem, text, and video. I don't think the Figma collateral currently specifies, but those three will cover most cases, and should characterize collections fairly well. I updated the Figma component to show that group. |
@jmakowski1123 @sdaitzman The sandbox was updated, fixing this issue. Could you please check it? |
Looks great, thanks for the fix! |
✅ In Scope:
Manage Tab: This will be defined in epic #1094, for now the tab just needs to exist in an empty state.
Details tab: The Details tab contains the following fields:
The text was updated successfully, but these errors were encountered: