# Statement of business value <!--- Outline the business value and/or return on investment that is the result of this proposal. ie. Implementing this change will increase Boost USD revenue by 25% in the next 90 days. ---> Optimising the display of Supermind posts on Twitter, by making them more visually appealing and eye catching, will convert more users to Minds and increase the revenue generated by Supermind # Scope <!-- MoSCow rules for prioritisation --> ## Must have <!--- For the goal to be met, it **must** have the following criteria. Ask the question ‘what happens if this requirement is not met?’ If the answer is ‘cancel the project – there is no point in implementing a solution that does not meet this requirement’, then it is a Must Have requirement. ----> - [x] The rich embed should generate a visually appealing image representation of the supermind text - [x] An endpoint that will generate the image based on the activity post guid ## Should have <!--- For the goal to be met, it **should** have the the following criteria. They are important but not vital. Without them the solution is still viable. One way of differentiating a Should Have requirement from a Could Have is by reviewing the degree of pain caused by the requirement not being met, measured in terms of business value or numbers of people affected. ----> - [x] A good caching policy for the images - [ ] Text should grow depending on available space and the size of the message - [x] The Minds logo should be included - [x] The username of poster should be visible ## Could have <!--- For the goal to be met, it **could** have the the following criteria. It is wanted or desirable but less important. These are the requirements that provide the main pool of contingency, since they would only be delivered in their entirety in a best case scenario. When a problem occurs and the deadline is at risk, one or more of the Could haves provide the first choice of what is to be dropped from this timeframe. ----> - [ ] Support for image posts ## Won’t have this time <!--- The below will be out scope and it not expected or required to meet the goal ----> - Avatars of the post owner # Technical Analysis <!--- This section will usually be filled out following the completion of a Spike or Analysis task. The criteria above must be sufficiently built out before the analysis can be completed. ---> Work has been merged in with https://gitlab.com/minds/engine/-/commit/892690baeff906c0796bed465832bf7e79635537 which has a proof of concept to generate the images.