Skip to content
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

View Fileset: Fixity Check button #692

Closed
2 tasks done
eporter23 opened this issue Dec 19, 2024 · 4 comments
Closed
2 tasks done

View Fileset: Fixity Check button #692

eporter23 opened this issue Dec 19, 2024 · 4 comments
Assignees
Labels

Comments

@eporter23
Copy link
Contributor

eporter23 commented Dec 19, 2024

When we added the Fixity Check button, we realized there wasn't much room to co-locate it with the current button set.

For this ticket, we want to:

  • Identify a better placement for the button
  • Restrict visibility of the button so that it only displays to Admin-level users
@CB987
Copy link
Contributor

CB987 commented Jan 2, 2025

some options for where the button can go:
i don't think it looks too bad with the buttons at the top
Screenshot 2025-01-02 at 4.28.32 PM.png

but could also combine the single-use link buttons into a dropdown?
Screenshot 2025-01-02 at 5.53.31 PM.png

at the end of the card title
Screenshot 2025-01-02 at 4.23.56 PM.png

below the thumbnail
Screenshot 2025-01-02 at 4.20.01 PM.png

turn the download and fixity check into an action items menu like on the works page
Screenshot 2025-01-02 at 6.21.00 PM.png

@eporter23
Copy link
Contributor Author

These are all good options! If it will fit on the top row of buttons that'd be great. Otherwise, let's place it below the thumbnail (but with a bit more top margin between it and the Download link)

@CB987
Copy link
Contributor

CB987 commented Jan 9, 2025

PR #700
Screenshot 2025-01-08 at 8.15.04 PM.png

@eporter23
Copy link
Contributor Author

Looks great @CB987 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants