<!--- 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 users to create Boosts (channel + activity Boosts) from the Boost console so that more Boosts can be made. ## What needs to be done Enable a user to create a Boost from the Boost console. - Channel Boost (can use existing "Boost channel" modal) - Activity Boost (can use new "Boost latest post" flow) ## QA <!--- Consideration is given to how the issue will be demoed and tested prior to being deployed ---> <!--- 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/W2xIag64EdbWUlGAQOpVHE/Boost-Update?node-id=1289%3A23979&t=4NEzNgVJFOP9qobH-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 ---> - [ ] Display the InFeed notice for the Boost Latest Post ## Definition of Ready Checklist - [ ] Definition Of Done (DoD) - [ ] Acceptance criteria - [ ] Weighted - [ ] QA - [ ] UX/Design - [ ] Personas - [ ] Experiments