This page demonstrates the opposite direction: a conversation authored in Discourse and presented safely inside WordPress.
Discourse remains the source of truth
The WordPress adapter retrieves this exact Bridge Record on the server. It validates the record identity and forum URL, sanitizes the bounded cooked HTML, caches it briefly, and renders only presentation content. The connection secret never enters the page or browser.
This discussion began in Discourse and is presented on the stock WordPress demo through an authenticated DiscussionBridge record.
The receiving plugin keeps Discourse authoritative for the topic, its author, replies, moderation state, and canonical forum URL. The WordPress adapter fetches the record on the server, applies a bounded cache and WordPress HTML sanitization, and returns presentation markup without exposing the connection secret to the browser.
That separation is the point of the demo: publishing platforms can present community knowledge without trying to become the forum or duplicating its identity system.
Reply here in Discourse and the forum remains the source of truth for the conversation.
What this proves: WordPress can present forum-authored material without copying forum ownership, sessions, moderation, or reply state into the CMS.