We are in the process of transferring one of our website from its hand-coded iteration into NetCommunity. Currently we have an account with a third-party – Slideshow Pro - where images are uploaded to their site to create a new ‘album’. A piece of javascript is added to the page to call the player. This third party offers a multitude of customisable options: Width, Height, Enable gallery browsing, Media player appearance, Automatically start playing videos, Slide duration, Looping, Scaling, Transition style, Caption appearance, Caption elements, Background colour, Background alpha, Media player background colour, Media player background alpha, Caption player background colour and Caption text colour. By using a third party, paid-for solution we know they are continuing to develop the product for their customer base. The NetCommunity part has poor presentation (using tables) and while the CSS may be worked to improve the look, it’s a lot of effort to achieve results we can get out-of-the-box with slideshow pro. Finally, should we want to use the slideshow on multiple sites (such as those that have a main site and an alumni site) we can enter the content (images and captions) once for slideshow pro and re-use the code. If we used the NetCommunity part we’d have to re-enter the content for other sites. Ideally, having a user-friendly front-end part to slideshow pro would give other users the flexibility to use a quality product.