Button below capped pool item (if its red) in the pools-table && grid view
The button launches a modal component
In the modal have the suggested tweet text with a copy button and some general info about posting it on Twitter and tagging which/what
Show an image of the capped pool in a layout/dimensions suitable to Twitter as an image-share (for the user to manually screenshot and share in the tweet)
Stage 2 (UX Improvement):
Add a 'twitter' icon button next to the copy button to open Twitter in the user's browser with the copied text pre-entered for them
Bonus but not critical: See if you can automate an image into the user's clipboard (or handed to Twitter API somehow) of the capped pool and implement that into the Tweet content too (this might be a bit problematic especially across browsers/OS/security-settings in terms of compatibility)
Think outside the box if the 'take a screenshot for the user' approach is problematic, ie: might alternatively be able to render the 'thing to be screenshotted' as an image instead of HTML (in the modal) for a right-click -> save/copy
Explore the options for better UX for the screenshot but dont stress too much if there is no clean solution, this is already an improvement in UX for Tweeting out capped pools even at stage 1
Stage 1 (Functional):
Button below capped pool item (if its red) in the pools-table && grid view
The button launches a modal component
In the modal have the suggested tweet text with a copy button and some general info about posting it on Twitter and tagging which/what
Show an image of the capped pool in a layout/dimensions suitable to Twitter as an image-share (for the user to manually screenshot and share in the tweet)
Stage 2 (UX Improvement):
Add a 'twitter' icon button next to the copy button to open Twitter in the user's browser with the copied text pre-entered for them
Bonus but not critical: See if you can automate an image into the user's clipboard (or handed to Twitter API somehow) of the capped pool and implement that into the Tweet content too (this might be a bit problematic especially across browsers/OS/security-settings in terms of compatibility)
Think outside the box if the 'take a screenshot for the user' approach is problematic, ie: might alternatively be able to render the 'thing to be screenshotted' as an image instead of HTML (in the modal) for a right-click -> save/copy
Explore the options for better UX for the screenshot but dont stress too much if there is no clean solution, this is already an improvement in UX for Tweeting out capped pools even at stage 1