Create wireframes for ChRIS Store Plugin/App Details screen

[mairin]

This is the page that you view the details of a single plugin listed in the store. Right now in @jdtzmn 's prototype, the following information is listed on this page:

• app name
• version number
• last modified date
• docker image
• description
• title

Other ideas include:

• Similar Plugins / Comparison Tool - One of the ideas @slsa22 had for this design was a tool that would show plugins there are similar to the one you're viewing, with perhaps a comparison grid. The use case being, a user trying to figure out which of a series of similarly-aimed plugins would be best for their needs.
• Screenshots - screenshots showing the type of output the tool can achieve
• Sample Data Sets - providing sample data sets to allow users just trying out the plugin to be able to achieve results displayed in screenshots and to give them an idea of what type of data works well with the plugin
• Categories / Tags - what kinds of categories or tags would help a researcher figure out how the plugin works / what it is for? Take a look at https://www.nitrc.org/ to see along what axes researchers consider these types of applications.

Any other ideas are welcome!

[mairin]

Some more notes from a discussion with Shania today:

• Use real data i would definitely fill in the mockup with actual images / icons / descriptions / etc. from an app so we can better understand how it'd look
• Plain tags use plain tags to start. the idea of custom icon tags is really intriguing but probably a lot more effort than we can do for a v1
• Color codes for tags? You could maybe consider color coding the tags based on what axis the tags belong to. For example, yellow for tags that indicate the type of image the plugin works with (eg MRI vs CAT vs Xray etc), green for tags that indicate something else...
• Two buttons There should probably be two buttons. One to link over to the plugin on docker hub, another that would let the researcher file a request with their local ChRIS admin to consider installing the plugin on their ChRIS instance.
• Try as much as possible to automate the collection of metadata about the plugin E.g. take a look to see if there's a way to indicate if a newer version is available upstream?