Userflow v1.0

Design v1.0

Names...
ZOO? EXPLORE? INTEGRATE?

Design...
The ZOO is accessed via a new button (identified by the binoculars icon) at the bottom - separated in a new container from the other MANAGE views as this feature is initially a dialogue.

The tooltip should identity the feature states - wether alpha or beta (depends on gliff-ai/style#214).

The dialogue is a very similar layout and component use/design to CURATE.

The first row has one container with plugin and image icon which allows the user to toggle between available plugins and datasets, and another container with sort icon which allows the user to sort the available content. The second row has one container with the search functionality via a select field and text field.

The gallery is a set of cards which offer a preview of a plugin/dataset. This includes: icon/image, name, creator, short description, details, See More and Activate buttons.

The sort data dialogue should list relevant sort categories. In this case I've exemplified: name, security (titanium, aluminium), architecture (front-end, back-end), and type (Python, Typescript, AI) - open to changes in this area, I'm aware I've likely used the wrong terminology to describe these categories.

The expanded gallery card offers more space for the plugin/datasets description.

The user can access the content gallery via the Go Back button or interacting with the gallery type view, sort or search functionality.

The question mark icon in grey allows the user to hover and learn more. Original discussion on the security of a plugin was to categorise them by metal - i.e. titanium and aluminium - however these aren't as descriptive. This space allows extended text to help communicate this rank to a user.

looks like it's time for search and sort to make their way to STYLE

Design v1.0 [continued]

The ZOO can also be accessed in CURATE via a new button (identified by the binoculars icon) at the bottom - separated in a new container from the other CURATE buttons at the bottom.

The tooltip should identity the feature states - wether alpha or beta (depends on gliff-ai/style#214).

@joshuajames-smith, we also need a button (or other UI/UX element) for publishing plugins, so a team can decide if they want to share their plugins with other teams. All plugins are private by default and only public plugins are displayed in the ZOO. For now I've added a toggle button to the "Plugins" table in MANGE: