-
Notifications
You must be signed in to change notification settings - Fork 2
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
Visibility Dialog #20
Comments
I think this looks good & the categories public / private / restricted make sense and can be explained in the new version of the collaboration page. We just need to update the action buttons as per our latest discussion @Grizzly127, otherwise I think this issue can be moved to be on the priority list (@HeyItsBATMAN). |
@Grizzly127 - great, this is a good idea. Window mockup looks good, only we should remove the "test 2" - object name shouldn't be visible in this step I think, only in the smaller dialog (I've noted that on Figma as well)
Not sure about the position here - might be better to take it out in the action bar - can you make several mockups - one with text, one with icon, and try out several positions? I noted on Figma that we lost track of what is the final object view action bar as we have several variants now with less / more icons.
Sure, makes sense.
Yes, agreed.
Agreed, we should get rid of the Publish button. |
I'm not sure here, because the title of the stepper is "New Object" all the time, because it is the process of adding a new object. Maybe rename it to "add new object", but the title of the object was not meant to be displayed here. We could still remove the object name, because the other settings also don't use the title name again |
Position of Visibility status
We could have it as a text next to the object and just write "Public", "Private" or "Restricted" We could have it as an infobox next to the object, maybe also with the possibility to come quickly to the settings: We could use the icons we are using at the settings: We could add an extra field for the visibility: We could integrate an icon for the status into the actionbar. Since it is not clickable (?) like the other icons and should just be an information, maybe with a tooltip (Infobox like in the screenshot or just "Private", "Public", "Restricted") I made it in blue. Sorry, due to time, I did not always display all options for Public, Private and Restricted. I hope this can still give you an idea about the options. When we decide for what we like most, I can mock up all statuses again. |
@Grizzly127 Good idea, let's change the dialog name to "Add new object". Then remove the object name below for consistency. |
@Grizzly127 Hm this thing with where we show the visibility status is quite tricky, we don't want it to be too obscure (I think in the action bar as a solo icon is a bit difficult to understand, then users are dependent on the tooltip text). At the same time it shouldn't be quite the same as metadata, because it's not visible to all users at all times - what if it's its own white box / section between the title section and the metadata section (it can also be below metadata, but if the user adds all categories of metadata, that pushes visibility quite far down, possibly below the scroll fold and that is not great, i think the visibility status should be instantly visible near the top of the page). We can even remove the "Visibility" heading, imagine a while narrow section with only a blue pill button that says "public / restricted..." etc and the grey outline info box next to it (not below) - that way the space is optimized a bit better and this visibility thing will anyway not be visible to non-owners, only owners of the object will see this section. If this makes sense and you can mock it up, would be great, just to see. |
Suggestion for the visibility dialog
before:

after:


"Online status" is about if the object is published or not. Since we use "Publish" at the object view to make an object visible for others, I would suggest using "Publish" here too.
@HeyItsBATMAN @ZetOE @lozanaross
The text was updated successfully, but these errors were encountered: