Ghost WP Bridge plugins authenticate against a Ghost Content API and pull posts, tags, and members into WordPress at a configurable cadence. Each synced post lands in wp_posts with provenance in wp_postmeta (typically _ghost_post_id, _ghost_url, _ghost_updated_at), members map to WordPress users via wp_usermeta (_ghost_member_id), and a small sync log tracks the last few hundred sync events.

The bridge's default admin surface is a settings page plus a sync trigger and log. It doesn't aggregate the synced inventory: there's no view of which Ghost posts changed since the last sync, which Ghost members haven't been resolved to a WP user, or which redirects from the old Ghost URL space to the new WP slug have stalled. Cross-cutting audits today live in SQL or in spreadsheet exports from both sides.

SleekView reads the provenance meta, the member-mapping meta, and the sync log together, then joins everything to wp_posts and wp_users. Out-of-date posts, unresolved members, and broken redirects become row-level cohorts; inline retries call the bridge's own sync handler so Ghost sees the same API calls it would on a scheduled run.

Running Ghost alongside WordPress is a common architecture once a publication outgrows either platform alone: Ghost handles the newsletter and memberships, WordPress handles the marketing site or the public archive. The bridge between them is the operational layer where things go quietly wrong: posts updated upstream don't propagate, members don't resolve to WP users, redirects from old Ghost URLs drift after a slug change. The bridge plugin's settings screen is fine for configuration but wasn't built to be a daily health dashboard, and the data needed to audit the sync, wp_postmeta, wp_usermeta, and a sync log table, lives where only SQL or a custom debug screen can reach it.

SleekView lifts that data into a row-level workspace with sync state, redirect health, and member resolution joined inline, and routes resyncs through the bridge's own handler. For publishers running two CMSs as one product, that workspace is what keeps the bridge auditable instead of accreting silent drift between the two sides.