The badges plug-in can be used to display badges, or a tag cloud, related to a table row by a one to many or many to many association.
For instance, let's say you have a table for blog posts and a table for topics, which contains a field "name" being the name of the topic. You would then create a join table PostTopic containing two foreign keys, one to the posts table and one to the topics table. Because this is a many to many relationship, each post can belong too many topics, and there can be many posts for each topic. You would then create a view with the Badges template. This view should be of the table of the primary entity about which we would like to display associated badges, in this case the posts table - NOT the join table (here, the PostTopics table) or the table with the label names (here, the topics). In the configuration, select the relation that gives the label for each of the badges. In this case it would be PostTopic.post->topic-> name, i.e. the field "name" from the table that is referenced by the "topic" foreign key field in the PostTopic table row. Then embed this view in a view of the posts, and you will see a little badge for each topic to which the post belongs.
This plug-in also provides the EditBadges view template which is similar to the Badges view template, except that it allows the user to edit the many to many relations by deleting and adding badges.
Views of the Badges and EditBadges view templates are rarely useful on their own and are usually embedded in other views or on pages together with other views.
Carousel views show table rows in a slider that changes every few seconds to the next row, with controls to go backwards and forwards superimposed. This is often used for slideshows on landing pages. The carousel is based on an underlying view, typically of a Show view, which must be template which you must first build, and must be of the same table as the table selected for the carousel view.
comment tree provides a view template that can show table rows with a hierarchical organisation in a threaded tree structure. It was designed to show threaded comments. The view is defined based on an underlying view of each item row, typically built with the Show view template.
a view template providing a location search bar based on a geocoding. Geosearch views are not typically useful on their own but are used on pages together with other views showing the results of the search, typically or feed or a list. The results will be shown ranked by proximity to the location found in the search bar
view template for kanban boards, where the view in each kanban card is based on another view you have defined with a different view template, typically Show. Cards can be dragged and dropped to be reordered inside a column or moved from one column to another. The underlying table needs a field to track column identity and optionally card location within the column.