As of today, we're starting to roll out our latest power feature: a native commenting widget. It serves the same purpose as say Facebook comments or Disqus. But with several massive improvements.
With the first comment entered into the widget window it creates a new post in your community and links the commenting thread on your external page to a community thread. As a a result, all our tooling for the community homepage, notifications, mentions, email updates, profiles, sign-in and everything else work, right out of the box! For example, when somebody replies and you're subscribed, you'll get an email and see a notification in your notification panel. Posts created by the widget will be bumped to the recent area in your community's newsfeed (if you want them to be). And much more.
First of all, if you're going to put the widget on pages that are not on your current community domain, you need to whitelist these domains. This is needed in order to prevent malicious actors from putting your widget on any website pages that you don't control, thus creating community posts and hurting your reputation. This is a very simple process, just go to Widgets -> Domain Whitelist and add the domains on you which you want to allow PeerBoard to place widgets.
Our widget works as a simple piece of JS code. All you need is a way to embed arbitrary JS into your web pages. If you're using a custom built setup, this should not be a problem. Most site-builders and CMSes also support JS embeds so just look for JS embed options in your CMS or site-builder.
You can find the code for embedding a widget in Widgets -> Commenting Widget from the Settings section of your Admin Panel.
We also are providing you with several ways to control the widget:
- You can assign a specific Space to receive the new posts created the widget. If no space is selected, we'll create a new "Discussions" Space as a default.
- (WIP, coming soon) You can pass defaults for post content which is especially helpful for private communities since we fetch our defaults via OpenGraph and this only works for public content.
- You can chose to treat different domains with same url paths as the same url for the purpose of creating new linked posts. This is helpful when you have multiple domains say for different locales, such as en.domain.com and es.domain.com.
- You can chose to treat different query strings on the same url path as different urls for the purpose of creating new linked posts. This is useful in some very rare cases like our Thinkific integration where we had to hack around their navigation limitations via query string parameters.
For programmatic or semi-programmatic setups, you can always just insert JS embed code from our widget configuration page. But if you are using our SDK for deep integrations, we recommend to use our native SDK component for commenting instead. This would give you a way to automatically provision member session even if they are not logged into the community yet and avoid unnecessary redirects. Read our guide on using SDK for commenting here.
- Deleting a community post linked to a page with our commenting widget will also delete the whole discussion, so be careful.
- If you want to hide discussion posts from your main feed. You can just put them all in a space that is not visible to your members in the feed by default. Control that from widget customization settings.
- If you're using an external login url. We will replace our embedded sign-in/sign-up flow with a chain of redirects: widget -> community page -> your login -> community page -> widget. Note that while it looks long, it needs to happen only once and if the member already visited community, it is shortened to 2 steps instead of 4.
- If you move the post to a different space. It will still be linked to the discussion that triggered its creation, regardless of the widget settings.
Post in the comments!