FlyingPress writes its page cache as static HTML files under wp-content/cache/flying-press/ and tracks its preload queue, used CSS, and critical CSS records in custom tables such as wp_fp_cache, wp_fp_critical_css, and wp_fp_used_css. Each row carries a status, a last_built timestamp, and a job identifier from the FlyingPress cloud service for critical CSS generation. The default FlyingPress dashboard exposes counters and Clear Cache buttons, which is fine for a healthy site and gives very little signal during an incident.

SleekView Kanban reads the same FlyingPress tables that the dashboard counters aggregate. Pick a derived flyingpress_state field that buckets URLs by cache file presence, preload queue membership, critical CSS job status, and used CSS status and every URL becomes a card grouped under Uncached, Preloading, Cached, or Critical Pending. Card fronts can show the URL path, the cache file size, the critical CSS job age, the used CSS status, and the last access timestamp so a developer can prioritize work without leaving WordPress.

Dragging a card between columns calls the FlyingPress helper. A move from Critical Pending back to Uncached resets the critical CSS job so the next preload pass re-requests generation. A move from Cached to Uncached purges both the page cache file and the critical CSS row for that URL. FlyingPress's own automatic invalidation on post save keeps running normally, so a manual board move and an automatic invalidation can happen in the same minute without leaving the caches inconsistent.

FlyingPress is fast and quietly busy. The dashboard exposes counters and Clear Cache buttons, which is enough for a healthy site and a blunt instrument the moment something looks off. Stuck critical CSS jobs sit in the queue invisibly until a user reports an unstyled flash.

Stale cache files quietly accumulate until disk usage alerts fire. Used CSS rows stall on a single URL and nobody notices until a Core Web Vitals run shows a sudden regression. By the time the developer has reconciled the dashboard, the tables, and the file system, the moment has already passed and the team is reaching for a global purge that wastes work.

A kanban view that reads and writes the same FlyingPress tables and helper methods as the dashboard keeps every moving part visible. Uncached, Preloading, Cached, and Critical Pending all live on one board. The team can act on individual URLs instead of clearing everything and waiting to see what rebuilds first.