DiscussionBridge Alpha Support

Bring the problem.
Keep the learning.

Alpha support lives with the community so a useful answer can help the next operator too. Start with the forum, whether you are installing The Bridge, connecting a platform, testing a demo, or finding an edge we have not seen yet.

Visit Alpha Support Read support guidance

Choose the shortest path

Start with what you know.

Versions & releases

Find the current product versions, download availability, public release record, and the exact installation guidance.

Find the current release

I need help

Ask in Alpha Support for installation, configuration, adapter, demo, or workflow help. Screenshots and sanitized logs are welcome.

Ask the community

I found a problem

Describe what happened, what you expected, and how to reproduce it. We will connect confirmed product work to the correct GitHub repository.

Report it in Alpha Support

I have an idea

Share the publishing problem and the outcome you need. Real workflows help us choose what belongs in DiscussionBridge next.

Join the roadmap discussion

A useful support request

Help us see what you see.

Include only what applies. A short, reproducible report is more useful than a large unsorted log.

Which DiscussionBridge product, adapter, and version you are using
Your publishing platform and Discourse versions, when known
The page, connection, presentation mode, or workflow involved
The exact steps that produced the result
What you expected and what happened instead
Sanitized error text, logs, screenshots, and relevant public URLs

Public support boundary

Keep secrets, private content, and personal data out of support messages.

The Alpha Support category is public. When email intake opens, its messages are intended to become forum support topics too. Assume the subject, message body, links, and attachments may be publicly visible.

Never send API keys, connection secrets, passwords, private server addresses, private content, database exports, access tokens, or unredacted configuration files.

From support to product work

The conversation stays understandable.

Discourse preserves the question, discovery, and community answer. When a report becomes confirmed product work, we link it to the appropriate GitHub issue so the public support context and the formal engineering record remain connected.

Explore DiscussionBridge on GitHub