Author: DiscussionBridge

  • The Bridge publishes everywhere

    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.


  • WordPress publishing through 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

    WordPress suppliesThe Bridge supplies
    Canonical article and authorDiscussion and moderation
    Headings, links, tables, quotes, code, and mediaDurable topic identity and replies
    DiscussionBridge content flow diagram
    Content stays on its publishing platform while discussion connects through The Bridge.

    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.