Choosing a Gallery and Slideshow Strategy for Evolution CMS

Projects that come back to Evolution CMS after a long pause often ask the same question: which gallery or slideshow module is the current favorite? The honest answer is that the right choice depends less on fashion and more on how the site stores images and how flexible the output must be.

Start from the content model, not the effect

• Do you need one image per resource or many?
• Are galleries attached to resources, products, or custom data rows?
• Does the site need editor-friendly uploads in the manager?
• Should the front end be a classic slideshow, a lightbox gallery, or both?

Common strategy options

• TV-based images for simple one-image or small multi-image setups
• gallery extras when editors need upload tabs and structured media handling
• DocLister-driven output when the gallery data already lives in resources or related tables
• front-end sliders as a rendering choice, not as the storage model itself

The important separation

A slideshow library and a gallery data model are not the same thing. One stores or organizes the images. The other only renders them. Keeping those roles separate makes future redesigns much easier.

Recommended approach

If the project is small, start simple: keep image data predictable and choose a front-end slider only after the storage model is clear. If editors need richer media workflows, use a dedicated gallery extra and let the front end consume that data cleanly.