Category: Uncategorized

DiscussionBridge keeps a discussion independent from any one CMS while letting each platform present the same forum-owned source as native content. This article is the canonical source for the first Discourse as Publisher demonstration.

One source, native destinations

The Bridge owns this article, its revision history, author, moderation, and replies. Each authorized adapter receives an exact source revision and materializes a genuine platform record—not an iframe and not a manually copied page.

The first publication set targets Astro, WordPress, Ghost, Statamic Flat, Statamic DB, Statamic SSG, and Hugo. Every destination retains its own native URL and platform identity while pointing back to this topic as the discussion authority.

Idempotent publication

A destination creates its native record once. Repeating the same publication revision is a no-op. Editing this first post advances the source revision, allowing each adapter to update the existing native record without changing its Bridge resource, destination URL, or topic.

flowchart LR
  B[The Bridge] --> A[Astro]
  B --> W[WordPress]
  B --> G[Ghost]
  B --> SF[Statamic Flat]
  B --> SD[Statamic DB]
  B --> SS[Statamic SSG]
  B --> H[Hugo]

Portable presentation, forum-owned discussion

Destination themes control typography and layout. DiscussionBridge transports bounded cooked content plus exact provenance. Replies remain on The Bridge and can appear through Simple, Full, or fullInteractive discussion modes without transferring moderation or login authority to a CMS.

This is the flagship workflow in action: publish once from The Bridge, materialize natively everywhere, and keep the discussion free.

Revision propagation

This controlled update proves that one Discourse revision updates all seven native platform records in place without changing their destination identity.

This page presents topic 56 in Simple mode while Ghost uses Full and Statamic DB uses fullInteractive for the same authoritative discussion.

One topic, three deliberate choices

The Bridge keeps one discussion. Each platform selects the presentation that fits its page, audience, and operating boundary.

One authoritative discussion

This is the WordPress destination for the shared Full mode demonstration. The same topic appears on all seven platform profiles through the standard Discourse comments presentation.

The host page remains WordPress. Discourse retains the discussion, sessions, moderation, and reply state.

One authoritative discussion

This is the WordPress destination for the shared Simple mode demonstration. The same topic appears on all seven platform profiles, while WordPress renders its replies as lightweight native comment cards.

Add a reply on The Bridge, then compare how one conversation travels without forcing every platform into the same visual shell.

This stock WordPress page demonstrates the standard Discourse comments presentation for a DiscussionBridge-connected article.

Discourse Core presentation

Full mode uses the ordinary Discourse comments surface. It is the familiar baseline between Simple native cards and the plugin-enhanced fullInteractive application frame.

The same durable discussion

The canonical WordPress URL and stable post identity continue to resolve one authoritative topic on The Bridge.

This stock WordPress page demonstrates DiscussionBridge Simple mode: the article remains WordPress-owned while public replies are presented as lightweight native cards.

A lightweight reader path

The first five replies appear immediately. Longer discussions disclose more comments without loading the complete Discourse application.

Forum authority remains intact

Profiles, moderation, reply permalinks, and the complete conversation still belong to The Bridge.

A WordPress article can keep its canonical home while The Bridge provides the durable discussion, moderation, and community surface.

Publish from WordPress

The author opts this article into DiscussionBridge before its first publication. WordPress sends the published title, canonical URL, structured body, and stable author identity through its protected server connection.

Keep one content identity

The article belongs to WordPress. The discussion belongs to Discourse. DiscussionBridge preserves the relationship between them.

Carry portable structure

Resolve safely

WordPress post ID + site identity → one Bridge Record → one Discourse topic

Retries reuse the same identity. Ordinary edits do not create another topic or pretend to synchronize an unsupported content update.

Continue in fullInteractive mode

The mapped discussion appears below this article in a bounded application frame. Reader sessions, replies, composer, moderation, and accessibility remain owned by Discourse.

A WordPress post can keep its editorial home here while DiscussionBridge gives it a durable, fully interactive conversation in Discourse.

Publish once, discuss where communities thrive

This article was created in a stock WordPress installation and explicitly opted into DiscussionBridge. On its first authoritative publish, the WordPress adapter sent the article’s stable identity, canonical URL, title, and published body to the receiving Discourse plugin.

• WordPress remains authoritative for the article.
• Discourse remains authoritative for replies, identity, moderation, and community features.
• Retries resolve the same Bridge Record and topic instead of creating duplicates.
• The connection secret stays on the server and never enters this page.

The bridge is visible, not magical thinking

Below the article, the native adapter presents the mapped Discourse discussion using Discourse’s full application and dynamic-height behavior. Readers can follow the conversation, sign in through Discourse, reply, and use the forum’s normal moderation and notification tools.

One publishing workflow, two systems with clear ownership.

DiscussionBridge stock WordPress demo

This is the stock demo: WordPress core presentation plus the bridge integration. Future showcase demos may add CodeWorksLabs themes, but the product proof here deliberately stays close to a normal WordPress installation.