Cascade CMS 8.24 was a feature release that landed in early 2024. Unlike a typical minor release, several of its changes were operationally significant for institutions running Cascade at scale. This post is a reference for what 8.24 added, why it mattered, and how it affected day-to-day Cascade operations in higher education.
Suggested Unused Assets Report
Institutions running Cascade for years tend to accumulate orphaned assets: images uploaded for a campaign that ended, old PDFs that no longer link from anywhere, draft pages that never got published. Over time these orphans clutter the asset library, slow down search inside the CMS, and make audits harder.
8.24 introduced a Suggested Unused Assets report that surfaces assets with no active references in the published site. Site administrators can review the report periodically and clean up the asset library without manually crawling the publish graph.
This was a useful piece of operational tooling. For institutions that have been on Cascade for five or more years, the first run of the unused assets report typically surfaces hundreds of cleanup candidates.
Enhanced Broken Link Reporting
The broken link report in 8.24 added two configuration options that mattered in practice.
Allowed URLs lets administrators whitelist specific external domains that should not be flagged even if they return non-200 responses, which was useful for partners that aggressively rate-limit crawlers but still serve content correctly to real visitors.
Valid Response Codes lets administrators specify which HTTP response codes count as "not broken," which matters for institutions whose third-party integrations return 401 or 403 when crawled but are actually working as designed.
The combination of these two options made the broken link report meaningfully less noisy, which made it more useful as an actual operational tool.
Siteimprove Prepublish Integration
Siteimprove is the accessibility and content quality platform most higher education institutions use for compliance scanning. Before 8.24, the Siteimprove integration ran post-publish: editors published, the site was scanned, regressions surfaced after the fact.
8.24 introduced prepublish integration. Editors can now check content against Siteimprove rules before publishing, which catches accessibility regressions and content quality issues at the moment they matter (during authoring) instead of after the issue is already live.
For institutions facing increasing accessibility compliance scrutiny, this is the kind of structural improvement that matters more than a hundred editorial reminders.
WebP Support
8.24 added WebP image format support to Cascade's image editor. WebP produces materially smaller files than JPEG or PNG at equivalent visual quality, which improves page load times and Core Web Vitals on the production site.
The configuration step is administrative: a .webp extension has to be added to System Preferences before editors can upload WebP files. Once configured, the image editor handles WebP the same way as other formats.
Page speed improvements compound on the production hosting side. The CDN serves the smaller files, the browser decodes them faster, and the LCP metric improves. WebP is one of the cheaper performance wins available to a Cascade Website Hosting environment.
Streamlined Content Checks
The content checks that run on submit were rebuilt for performance. The redesigned flow reduced the number of clicks and the perceived wait time during the publish workflow, which was a quality-of-life improvement that compounded across thousands of daily editor actions.
This was not a headline feature, but for institutions with hundreds of named editors, faster content checks translated into measurable productivity gains.
File Extension Change Warnings
8.24 added warnings when editors changed file extensions in ways that would break inbound references. This addressed a class of mistake where renaming a .html file to .aspx would silently break links from other parts of the site.
The warning prompts the editor to confirm the change and, in most cases, prevents the link breakage before it happens.
Performance and Stability
Behind the scenes, 8.24 included memory efficiency improvements for large file uploads, faster asset location through the Velocity Locator Tool, and improved audit log loading. None of these are user-visible, but they meant Cascade scaled more comfortably on the same hardware.
The release also upgraded internal libraries and the Software Bill of Materials (SBOM), and updated OpenJDK and the Quartz scheduling library. For institutions whose security teams audit dependency CVE coverage, the upgrade closed several open findings.
Accessibility Improvements
8.24 improved keyboard navigation and screen reader support for the asset More menu and a few other administrative surfaces. The CMS had always been usable with assistive technology; 8.24 closed several remaining gaps.
What 8.24 Did Not Change
The release did not change Cascade's publish model, the templating languages, or the API surface in incompatible ways. Institutions on supported platforms could upgrade in place from 8.23 with a database backup and a standard upgrade procedure.
The production hosting tier (the Cascade Website Hosting environment that receives published output) did not need changes. Existing CDN, web server, and infrastructure configuration continued to work.
Frequently Asked Questions
What was the most useful new feature in Cascade 8.24?
The Siteimprove prepublish integration. For institutions facing accessibility compliance pressure, catching regressions before publish is structurally better than catching them after publish.
Did Cascade 8.24 require migrating templates or content models?
No. The release was backward compatible with 8.23 templates and content models. Institutions could upgrade without template work.
How does WebP support in Cascade affect my production hosting?
WebP files are smaller than equivalent JPEG or PNG, which means faster delivery from the CDN and better Core Web Vitals on the production site. The production hosting environment serves WebP automatically once Cascade publishes the files; no infrastructure changes are required, though the CDN configuration should ensure correct content-type headers.
Did 8.24 introduce any breaking changes?
No breaking changes. The Delete option for the LDAP Configuration Orphaned User Behavior continued the phase-out that started in 8.23, which affected institutions still relying on it for LDAP sync cleanup.