WP Email Template wraps every outgoing WordPress email in a branded HTML layout. Each template is either a custom post type row or a serialized entry in wp_options, depending on the version, with metadata for template type (default, password reset, new user, custom), CSS overrides, active flag and last modified date. The plugin filters wp_mail and inserts the matching template at send time.

The plugin admin lists templates one per row with edit and preview links. It does not aggregate. How many templates exist, how many are active, which template types are overridden and which fall back to default, when the active set was last edited: each of those is a useful operational question, and the default UI answers none of them at a glance.

SleekView Charts reads the WP Email Template rows directly. A Number card anchors total active templates. A Pie splits templates by type (default, password reset, new user, custom). A Bar ranks templates by edit count or by last_modified recency. An Area trends template edits over time, surfacing the months the branding team was active versus the long stretches of "nobody touched this since launch."

WP Email Template ships when a brand team needs every WordPress email, from password resets to comment notifications, to feel like the product. The trade-off is that the plugin's surface is a per-template editor, not an inventory view. A template that fell back to default after a plugin update, a password-reset email still wearing the bundled layout, a custom HTML override that hasn't been touched since the brand refresh: each of those is a small but real branding miss, and the plugin admin doesn't surface them as a list.

Charting template count, type mix and edit cadence turns the branded-email program from a folder of files into something a brand lead can audit in one screen. Same WP Email Template data the runtime filter already reads, framed as the dashboard the brand team actually wants.