W3 Total Cache splits its work across several stores. The page cache disk store lives under wp-content/cache/page_enhanced/ with one HTML file per URL. The minify store writes hashed bundles under wp-content/cache/minify/. The CDN push queue tracks file uploads in wp_options under a serialized w3tc_cdn_queue array, and the preload schedule sits next to it under w3tc_pgcache_prime. The default Performance dashboard exposes an Empty All Caches button and a counter, which works on a small site and hides every interesting detail the moment a single cache layer misbehaves.

SleekView Kanban reads the same disk folders and option rows the dashboard aggregates. Pick a derived w3tc_state field that buckets URLs by page cache presence, preload queue membership, minify bundle status, and CDN upload state and every URL becomes a card grouped under Uncached, Preloading, Cached, or Stale. Card fronts can show the URL path, the page cache file size, the minify bundle hash, the CDN upload status, and the last write timestamp so a developer can spot bottlenecks across the cache stack without leaving the board.

Dragging a card between columns calls the W3 Total Cache helper API. A move from Stale back to Uncached purges the page cache file and re-queues the URL for the next preload tick. A move from Preloading back to Uncached cancels the in-flight task. W3 Total Cache's automatic purge on post save keeps running, so a manual board action never collides with the plugin's normal cache invalidation flow.

W3 Total Cache is one of the oldest and broadest cache plugins on WordPress. The Performance dashboard juggles page cache, minify, object cache, database cache, fragment cache, browser cache, and CDN push under a single tabbed interface. The breadth is what makes it powerful, and the breadth is what makes it hard to operate at scale.

An Empty All Caches button hides the fact that only the minify bundle for a single template is broken. A CDN upload counter hides the fact that one large object has been pending for an hour. The team relearns these blind spots every time a launch goes badly.

A kanban board flips that around. Every URL is a card. Every combined cache state is a column.

A glance at the board tells the team how many URLs are uncached, how many are stuck in preload or CDN push, how many are stale past their TTL, and which paths dominate each group. Dragging a card writes the change back through the same helpers the dashboard already trusts. The Empty All Caches button still exists, and still works as a last resort.

The board exists for the rest of the time, when the team needs to see the cache stack the way the cache stack already sees itself.