WP Newsletter Builder, the Alley-maintained plugin, models newsletters as a Gutenberg-authored custom post type. Newsletter content is composed from a dedicated block set: a subject block, header, ad blocks, post-list blocks and custom layout blocks. Each newsletter post carries postmeta for template selection, sender list and send-to-ESP routing.

The plugin's admin focuses on authoring inside the block editor and connecting to Campaign Monitor or the configured ESP. There is no editorial table that lists every newsletter across draft, scheduled and sent statuses with template, sender list and author as real columns. Editorial leads who want to scan the pipeline have to sort the post list and click into rows for the routing detail.

SleekView reads the newsletter CPT and its postmeta directly. Title, template, sender list, status, author and post date sit as real columns. Sort by post_date for the cadence, filter to status=draft for the backlog, bulk-flip stalled drafts to trash without opening each post.

WP Newsletter Builder, used heavily by publishers, ships an excellent Gutenberg authoring surface and a serious ESP routing pipeline, but it is authoring-first by design. Editorial leads who need to know how many newsletters shipped, which template is doing the work and whether the cadence is holding are stuck inspecting the post list. SleekView reads the same CPT and postmeta the plugin already writes and renders the editorial picture as a sortable, filterable table.

Template usage becomes a sortable column, status mix becomes a filter and cadence becomes a date sort. The data is already in WordPress, the table layer turns the authoring tool into an operational workspace without changing how a single newsletter gets written.