This section of the test area show all of the collection layout styles that are available in the current CSS layout framework. If you don't see it here, it's not part of the core CMS in this version release. It may be possible to mix and match some of the class names so feel free to experiment, but if you don't see it in one of the examples then you shouldn't rely on it working in all contexts on all screen sizes, or being suppoted in a future CMS release.
The test articles in this container are unstyled. These articles are the ones used in other layout tests in this section of the test area.
Different cards layouts: standard, padded, fixed image size, landscape, panorama, date overlay, cards in two & three columns blocks, smaller cards.
Simple, plain articles/containers in three columns.
Simple, plain articles/containers in two columns
Images are on the left, text is on the right. It's pretty simple. But it can look great in the right moment.
Image Right is like Image Left, but many would argue that it's more right.
Alternating between Image Right and Image Left in a collection of articles
Add the class "link-cover" to a content collection to turn the entire item into a single link.
This page is for testing the masonry layout.
The masonry layout goes up and down instead of sideways.
This container has many pages in it, so that we can see what the paging layout looks like along with the article dropdown filter.
The postcards style is a subset or cards, so the classname is "cards postcards".
The timeline widget is a nicely styled version of ArticlesInSubContainers.
Tiles are a little like image-left but styled differently, and the image fills/covers the side box.
This is for testing all article widgets, including Article, Articles and Articles In Sub Containers, using web page, product and event articles.
This is for testing all container widgets, including Container, Containers and Containers In Sub Containers, using web page and product containers.
This is for testing summary views for containers and articles widgets on the same page, ensuring all summary fields are displayed correctly.