We've redesigned the display of FanShots in the river to expose the content of the FanShot directly on the front page (i.e. show the video if it is a VideoShot or show the full image if it is an ImageShot). We want your communities to be able to engage with the actual content of the FanShot on the front page. We've also added share and rec functionality to the front paged FanShots to help boost social engagement. Here is a screenshot of the new river FanShots:

We've also redesigned the FanShots index page. Instead of the grid view that we have right now, we're going back to a reverse chronological view of all FanShots as the default. It's easier to scan and we have again exposed the key content directly on this page. Here is a screenshot of that page:

We've also cleaned up the entry view of each type of FanShot. These pages were just a bit messy and also inconsistent. We've put in some work to make sure they have a sharper look overall. Here is a sample screenshot:

As you might have gleaned from the screenshots, we've also given each type of FanShot an optional headline field, allowing site editors to add a headline to any FanShot you promote to the front page if you want.

Finally, we made some changes to the Linkshot type to improve the display of tweets that are shared in FanShots. LinkShots will now automatically format links to Tweets as embedded Tweets. When a user (or editor) creates a LinkShot by pasting in a Tweet link, the published FanShot will show the full content of the Tweet in the river, on the FanShots page, and on the detail page.

There are a couple of requested improvements that this release does not directly address that I wanted to point out and explain:

1. FanShots in the cover. Due to the variety of FanShot types and the structure of cover templates, placing and displaying FanShots in the cover turns out to be pretty complex. We do have some ideas here that we'll be working on soon, but we did not want to delay the release of the other river and detail page improvements out into the wild, so y'all could use them ASAP.
2. The placement of the FanShots widget on the home page. Some site editors have asked if the FanShots widget could be moved up higher on the home page. This is something that we are still considering (maybe the top rock is tabbed rather than just FanPosts; maybe that can be set on a site by site basis). However, that work will have to wait until we finish a major front-end code refactoring project that is currently in progress, but won't be finished until April.