Collection pages are display pages for content item from a given collection.
Problem: Collections (content sets) as designed today could contain really heterogeneous icontent types like blog entries with title, description, and images but also case studies with company name, testimony etc. In that case it is really challenging to display the Collection because the common elements are not numerous.
Goal: The goal of this story is to solve the above pb by guiding the user during the creation of collections (content sets).
When the user is creating a new collection
Then the user is proposed to select a single content type (ie) Asset Entry Type (& SubType if available) by default.
Note 1: With this change we are not preventing the user to select multiple content types but encourage the user to select one only.
Note 2: In case the user decides to create the set with multiple content types a warning should tell him that he will not be able to use it in a page that uses collection fragment.
Note 3: We are also renaming AssetEntries tp Collection Items. And few other renaming.
Figma mock ups are not up to date (refer only to story)