-
Notifications
You must be signed in to change notification settings - Fork 869
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
Make pinning hashes more intuitive #593
Comments
Of note, this is a useful data point for https://github.com/ipfs-shipyard/ipfs-ui-style-guide as it should define some of these things |
Hey @olizilla! You're right: the current interface is not the best and doesn't speak for itself. Would you mind to do some kind of sketch to show the way you think the form should be? 😄 |
@olizilla any updates on this? 😄 |
I suggest wait for canonical icons for pin actions: ipfs-inactive/ipfs-ui-style-guide#3 (comment) |
The checkmark and the green color together make it seem like it was successful before the user even interacts. It always makes me pause when I see it. |
Ditto. Let's create better UI for pinning!
|
Closing as unrelated to the newer version. |
Right now, the pin hash feature requires the user to enter an optional title and a hash and click the check mark to confirm.
It's not obvious from the UI that the user needs to fill anything out in the green bar.
We can make this more intuitive by:
As the title is optional, to make the action feel simpler, we could simply let the user enter a hash, pin it, and then make it easy for them to add a label while it's pinning.
If you try to pin a hash you already have pinned, we should informed the user, and scroll to the item in the list. Right now the new pin name (or empty name) overwrites any existing label you might have.
To be able to label an unlabelled pinned hash the user needs a way of previewing or opening the file to see what it is.
The add pin icon might be more intuitive in the top right corner, as a button with text for "Add". This applies to the "Add files" action on the files pane too.
The text was updated successfully, but these errors were encountered: