Cache Enabler is free and open source. SleekView reads the on-disk cache directory and the exclude rules through the plugin's public helpers, which means the kanban renders the same way whether or not you also run the KeyCDN add-on for the CDN integration on top of the static cache.

Yes. The drag handler calls the Cache Enabler clear helper for that URL, which deletes the matching HTML file from the cache directory on disk. The next visitor request to that URL forces Cache Enabler to regenerate the static cache from the live PHP page render output.

Yes. Cache Enabler honors the TTL setting from its options page, which automatically expires files past the configured age. SleekView surfaces the expired lane so you can spot URLs that crossed the TTL boundary, but the cache directory still self-prunes without manual intervention.

Yes. SleekView views are configuration only, so you can build one board filtered to blog URLs and another to WooCommerce URLs from the same Cache Enabler dataset. Each developer picks a default board, and admins pin shared boards into the sidebar for the whole team.

SleekView reads the exclude rules on every page load, so a URL that newly matches an exclude pattern shows up in the excluded lane automatically. The cached and uncached lanes shrink accordingly, and no kanban reconfiguration is needed for the exclude rule change to take effect.

Each cached card opens a side panel showing the response headers that produced the cache file, the minify state for HTML, CSS, and JS, the cache file size, and the mobile variant flag. Developers can inspect a URL without leaving the kanban to dig in the server cache directory.

Yes. SleekView respects WordPress capabilities, so you can require a senior developer capability before a card lands in the uncached lane for production-tagged URL patterns. Juniors purge staging URLs freely, but only seniors purge production URLs from the kanban.

SleekView reads and writes the existing Cache Enabler cache directory and option rows without adding shadow tables for cache state. View configuration sits in its own small options row, so uninstalling SleekView leaves every cache file and exclude rule exactly where Cache Enabler wrote it.