<!--- Please read this! The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor Before opening a new issue, make sure to search for keywords in the issues filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate. ---> ## Goal Enable aggressive, confident experimentation with Groups as a vehicle for user retention by refreshing the home feed screen to use modern design system and UI. ## What needs to be done Refresh the home feed layout for web + mobile app using the modern design system. Include a solution for managing settings for the group.  Assume that functionality available on the members list screen can continue to be served by the existing page without refreshing it, since that page isn't critical to Groups usability for most users. ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> ## UX/Design <!--- Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged. ---> [Figma](https://www.figma.com/file/ejrtrI9rNJjZYUcVw8U5iS/Groups-Refresh?node-id=21%3A1152&t=8b0JMH5PdAF4aYmz-1)    ## Mobile <!--- Does a mobile card need to be created? Any notes for mobile? ---> - [ ] Is Mobile Required? ## Personas <!--- Who does this user impact and why (optional) ---> ## Experiments <!--- Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined. ---> ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] ... ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments