In order for the feed to be engaging and interesting we need to be smart about tile formats and how the feed adapts.

The CMS has the ability to set the tile format for the topic, which should be the “prefered” format.

However the client should be smart enough to override these settings with the aim of avoiding the same layouts to appear in a row.

Topics should adapt based on the count of data within them.

We should adapt the UI for chosen UI defaults automatically when we lack the correct amount of data for the format.

A basic example would be not showing “See all” when the card can display all topics within the UI component (without scrolling)

For Topic 1, the default UI might be a horizontal scroll of round logos, but this UI component requires at least 5 tiles, so should fall back to sane defaults if less than 5.

The feed will be quite a drastic change for users during MVP testing and we will want to make sure everything they had access to previously still exists.

We should take the existing “Featured” content and make sure that they exist as tiles, and exist high up on the feed at the beginning for initial users.

We can slowly begin to sink these deeper down the feed as more relevent and important topics start to rise to the top.