Newsletter by Stefano Lissa, often called Newsletter plugin in the WordPress directory, ships its own subscriber storage, list management, queued sending engine, theme composer, and open and click tracking through tables like wp_newsletter, wp_newsletter_sent, and wp_newsletter_emails. Many sites also expose a public archive of issues, either through the plugin's archive shortcode or through a separate WordPress post for each issue. Those archive URLs are forwarded, embedded in Slack channels, and shared by subscribers as references.

SleekPixel reads the issue's post fields, the subject line as the headline, the send date as the publish date, the issue number from a custom field or a slug, and renders a per-issue card. The og:image and twitter:image tags get written into the head on save, so the archive URL previews as the issue itself when reshared. For sites running the Newsletter plugin's wp_newsletter_sent tracking to measure engagement, the card refresh keeps the public archive visually aligned with the in-inbox version, even though the email and the web archive are separately formatted.

Issue cards can also include a subscriber-count slot and a list label, useful when multiple newsletter lists from Newsletter's list management share the same archive structure.

Newsletter publishers spend most of their effort on the inbox version, the subject line that drives open rate, the layout that drives the click, the segments that drive deliverability. The public archive is often an afterthought, surfaced by a shortcode or a custom post type and otherwise left to the default theme. That is fine when the archive only carries direct traffic, but the moment subscribers start forwarding archive URLs as proof of value, or partners start embedding archive links in Slack channels as references, the share preview matters.

By default that preview is the site logo, identical for every issue, which leaves the recipient guessing which issue is being referenced. SleekPixel renders a per-issue card from the issue's post fields: subject line as the headline, send date in the meta line, issue number as the mark, list label as the badge. The card writes on save into the archive post's head.

Newsletter continues to handle subscriber storage, list management, queued sending, and tracking through its own tables and engine. The two plugins do not share configuration, and the result is a public archive that finally looks like the inbox content it is mirroring.