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), active flag, override flag, CSS customisations and last modified date. The plugin filters wp_mail and inserts the matching template at send time.

SleekView reads both storage paths and renders one row per template: title, template_type, active flag, override flag, last_modified and stewardship metadata. Filter to template_type=password_reset to confirm the reset email isn't still on the bundled default. Sort by post_modified to find layouts no steward has touched since launch. Filter to override=false on a given type to surface every transactional path that still falls back to the bundled layout.

The plugin keeps owning the wp_mail filter and the template editor. The table view owns the inventory surface, so the branded-email program stops being a folder of per-row screens and becomes something the brand lead can audit in one sortable grid.

WP Email Template ships when a brand team needs every WordPress email, from password resets to comment notifications, to feel like the product. The plugin handles the wp_mail filter and a per-template editor, and that's where its surface stops. After the first few campaigns, the inventory accumulates: legacy options-array rows from before the CPT migration, transactional types that fell back to default after a plugin update, custom HTML overrides that haven't been touched since the brand refresh.

Each of those is a row in the plugin's own data, and the per-row editor doesn't surface them as a list. SleekView reads the same CPT, options array and postmeta the runtime filter already uses, then renders the result as a sortable admin grid. The plugin keeps owning the editor and the wp_mail filter; the table view owns the audit the brand lead actually wants.