-
Notifications
You must be signed in to change notification settings - Fork 49
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
ChRIS Store: Update plugin details page design to account for README display, parameters, and version listing #81
Comments
Here is what the plugin details screen looks like when you first come to it. The orange/yellow labels show where the data comes form from the API. Items in orange are in the plugin-meta object, items in yellow are in the plugin object and need to be made available for the plugin-meta as well. There are three main tabs on this screen:
Overview tab visibleParameters tab visibleVersions tab to be uploaded in another comment when complete. |
@mairin These look great! |
I like it. Overview pageI like the following parts. It's user friendly.
|
List of mockup issues to address:
|
Here's a good set of mockups that addressed all of the above except the public repo field editing - I am thinking just an inline editable form field triggered by a link next to the field on the front page, only visible by a logged in admin? @jbernal0019 I'd love a review of these if you wouldnt mind! Front Page / README TabParameters TabConfiguration Tab |
Nice @mairin! Yes, the link to edit public repo should only be visible by a logged in admin. |
@mairin There should also be a way for a logged in admin to add a new admin given the ChRIS store username. |
@mairin Nice design. |
@jbernal0019 @anujsingla could we handle the case of a logged in admin adding a new admin (or removing a current admin?) similarly to public repo editing noted above... if you're admin and logged in, you'll see a "add new admin" link at the top of the admin section, and maybe little (X) buttons next to each admin to delete individual admins (with a conf dialog?) |
@mairin Yes, I think a logged in admin should see an "add new admin" link that allows him to add a new admin to the repo. Currently, once a new admin is added to the repo it can not be deleted as that admin might have published new versions of the plugin. One admin can not delete another admin. |
I had opened #103 to track adding the ability to add a new admin to the repo. Closing this since it's merged. |
(@mairin)
The text was updated successfully, but these errors were encountered: