Frontpage sludeshow

An image carousel (a client-side JavaScript slider) is the right pattern for a front‑page slideshow. @Minolwen was on the right track. For @javlonchik — because the site is ASP-based and editors update content manually, have the server produce the slide data (HTML or a small JSON feed) and let a JS slider render it. That keeps content editable without changing templates or redeploying.

Two practical server patterns: server-rendered markup (Repeater/Razor) or a JSON endpoint the client fetches. Example ASP.NET MVC action that enumerates an images folder and returns a simple JSON array:

public ActionResult SlidesJson()
{
    var folder = Server.MapPath("~/slides");
    var files = Directory.GetFiles(folder)
        .Where(f => new[] { ".jpg", ".png", ".gif" }
                     .Contains(Path.GetExtension(f).ToLower()))
        .Select(f => new {
            src = Url.Content("~/slides/" + Path.GetFileName(f)),
            title = Path.GetFileNameWithoutExtension(f)
        });
    return Json(files, JsonRequestBehavior.AllowGet);
}

Workflow tips: keep images in a /slides folder plus a small index.json editors can update, or add a tiny admin page that uploads and sets Title/URL/Alt/Order into a Slides table. Always include alt text and textual captions in the DOM (helps SEO and screen readers). Optimize images (multiple sizes or srcset), use lazy loading, and set a fixed aspect-ratio container to avoid layout shifts and flicker. Test initialization timing so the slider waits for image dimensions when needed.

Pick a maintained frontend slider (examples: Swiper, Slick) and verify keyboard controls, pause/resume, and ARIA behavior (see the WAI-ARIA carousel guidance at WAI-ARIA carousel example). @almostbob was correct that server code removes the need for manual template edits; @topsarge’s point about using ready-made scripts is practical — choose one that is mobile-friendly, accessible, and actively maintained.