BunnyCDN for WordPress writes its configuration to wp_options under keys like bunnycdn_url, bunnycdn_include_extensions, bunnycdn_exclude_extensions, and bunnycdn_excluded_directories. Pull zone details (zone name, hostname, region overrides) sit alongside the rewrite rules. The plugin's admin presents these as a settings page with text inputs and comma separated lists, which is fine for one time setup but offers no row view, no per pattern metadata, and no audit trail.

The result is that exclusions and includes drift. A path gets added during a launch, an extension gets excluded to work around a font issue, and a year later nobody remembers what is active. There is no way to see how many URLs each pattern affects, no way to filter by type, and no surface for delegating CDN tuning without granting full manage_options.

SleekView reads the BunnyCDN options and unpacks them into rows. One row per included extension, excluded extension, or excluded directory, with type and scope columns. Inline edits write through the same option API the plugin uses, so the runtime stays consistent. Saved views like Active includes or Excluded directories can be scoped per role.

Bunny is one of the more affordable CDNs for WordPress, which means the BunnyCDN for WordPress plugin ends up running on a lot of price sensitive sites. Those sites tend to grow without formal audit processes. Configuration drifts over months and years, patterns get added by whoever was on call during a fire, and the team that owns the site at year five is rarely the team that set it up.

The plugin's settings page is fine for the initial wire up, but it offers no surface for periodic review. Includes, excludes, and directory rules read as comma separated strings with no metadata. A queryable view turns that state into data.

SleekView reads the same options BunnyCDN for WordPress writes, unpacks them into rows, and presents them as a workspace that supports sort, filter, and inline edit. CDN audits move from quarterly chores to ten minute reviews.