<!--- 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 Increase engagement and new channel discovery by increasing visits to the Discovery tab. ## What needs to be done - Add a notification dot on the nav icon for Discovery that indicates new content. - When the user navigates to Discovery, the dot is cleared - The dot stays cleared for 24 hours ## 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/tHjd7fqgBiiTHRTNq5Ltfp/Web---Composer-and-Sidebar-updates?node-id=223%3A7879&t=89HUIWTvGeOE6Dx0-1) contains animation and hover states  **Spec sheet**  ## 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. ---> - Implement as an A-B experiment - Measure visits to Discovery page ## Acceptance Criteria <!-- Everyone should be able to understand what is expected to be delivered ---> - [ ] Add a notification dot on the nav icon for Discovery that indicates new content. - [ ] When the user navigates to Discovery, the dot is cleared - [ ] The dot stays cleared for 24 hours - [ ] Run as an experiment ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments