Discourse forums on any website.

One of the most under-appreciated design choices in Discourse is that every public page on every Discourse forum returns JSON when you append .json to the URL. Visit https://meta.discourse.org/latest in a browser and you get the human Topic list. Visit https://meta.discourse.org/latest.json and you get the same Topics as a structured JSON response with all the metadata you would ever need: title, slug, posters, replies, views, like_count, last_posted_at, created_at, Category id, tags, trust-level of the original poster, accepted-answer status, pinned status, archived status. The pattern works for every page. /categories.json returns the Category tree. /c/feature/13.json returns Topics in the feature Category. /tag/release-notes.json returns Topics tagged release-notes. /t/some-topic-slug/12345.json returns the full Topic with all replies. /top.json?period=weekly returns the top Topics this week. /search.json?q=schema returns search results. This was a deliberate API-first choice from Jeff Atwood and Robin Ward back in the 2013 launch, and it is the reason Discourse has the richest third-party tool ecosystem of any forum platform. The Poper Discourse Feed Widget reads exactly these public endpoints. No OAuth, no developer registration, no API key required for public Topics. We poll your forum's .json endpoints on a schedule (every 6 hours on Free, every 30 minutes on Pro), parse the JSON, cache the result on a global edge with a 97% hit rate, and serve it to your widget. The forum sees a single request per cache window instead of one per page view on your site, which means embedding is friendly to your forum's performance budget no matter how much traffic the embedding page gets.

Discourse's trust-level system (TL0 through TL4) is one of its smartest features and the reason serious communities choose it over open-everyone alternatives. TL0 is a brand-new account that just signed up. TL1 (Basic) earns automatically after reading 5 Topics, spending 10 minutes on the forum and similar low-bar engagement. TL2 (Member) earns after consistent participation over 15 days. TL3 (Regular) is granted to the top contributors who consistently post quality content. TL4 (Leader) is manually granted by admins to staff and trusted moderators. Every Topic and Post returned by the JSON API includes the original poster's trust level, which means a feed widget can filter on it. This is the killer move for brand-safe embeds. If you embed an uncurated /latest.json on your homepage, you might surface a TL0 spam Topic before a moderator catches it. If you restrict the embed to TL2+ regulars, you cut new-user noise by roughly 70 percent while retaining 90 percent of meaningful engagement. If you restrict to staff-only, the embed becomes a curated official-answer surface that can confidently sit on a corporate help center. The Poper widget supports a multi-select trust-level filter so you can mix tiers (for example: TL2+ for the Topic original-poster, TL3+ for accepted-answer, staff-only for pinned announcements). Most other Discourse embed tools either skip trust-level filtering entirely or only support a single floor value, which is why their feeds end up looking spammy on production sites. Trust-level filtering plus tag filtering is also the cleanest way to build a public roadmap embed: pull the #feature-requests Category, tagged accepted, original-poster TL2+, sorted by like_count, and you have a self-maintaining Top Voted Features list with no moderator workflow.

In late 2023 Google launched the Discussions and forums search feature and the Forum filter, both of which surface threads from Reddit, Stack Exchange, Quora and Discourse instances prominently in commercial-intent queries. Discourse forums now appear in roughly 25 percent of high-intent product-support queries on Google, and many of those Topics outrank the brand documentation pages they discuss. The technical mechanism is Schema.org's DiscussionForumPosting markup, which Discourse emits natively for every Topic and which Google specifically rewards with rich-result treatment. Most embed widgets ignore this on the embedding side. The Poper Discourse Feed Widget emits DiscussionForumPosting JSON-LD for every Topic it renders, with author (the original poster's username), datePublished, replyCount (or interactionStatistic for likes), articleBody (the first post excerpt) and a sameAs link back to the canonical Discourse Topic URL. The result is that your embedded Topic block on your marketing page is eligible for the same Discussions rich-result treatment as the original on the Discourse domain, which is a meaningful SEO win on product-comparison and help-center pages. The widget also respects Discourse's own canonical URL convention so your embed never competes with the source for ranking, which both protects your forum's organic traffic and satisfies Schema.org's attribution requirement for DiscussionForumPosting markup.

Discourse ships two official embed mechanisms out of the box and they cover different jobs. The first is the embedded comments script (Discourse embed.js), which lets you replace your blog or article comments with a Discourse Topic. You drop a small script tag at the bottom of a blog post, the script creates or finds a matching Topic on your Discourse instance, and visitors comment on the post via the Discourse Topic without leaving the page. This is excellent for blog comments and weak for everything else: it is single-Topic only, it requires anonymous-posting setup on the forum, and it does not give you any control over which Topics appear where. The second mechanism is the Category JS snippet, a small embedded list of recent Topics from a single Category. It is read-only, latest-sorted, and offers minimal styling control. Both official mechanisms work fine for what they are. A third-party Discourse feed widget like Poper covers the long tail of jobs that those two leave undone: multi-Category and multi-tag merged feeds, trust-level filtering, custom sort modes (Top with time windows, Hot, Solved-only), staff-only views, custom layouts (cards, masonry, roadmap), brand-themed CSS, edge caching with a 97 percent hit rate so your forum is not hit on every page view, and DiscussionForumPosting JSON-LD for SEO. The Poper widget is the right answer when you are embedding multiple Topics on a marketing page, a help center, a roadmap, a homepage social-proof block, or a customer portal. Use embed.js when you want Discourse to host comments on your blog. Use the official Category snippet when you want a quick read-only list with no customization needs.

When you choose Discourse for your community, you are choosing a fundamentally different relationship to your data than you would get from Reddit, Circle.so, Slack Communities or any closed forum platform. Discourse is open-source MIT-licensed software founded in 2013 by Jeff Atwood and Robin Ward (Atwood previously co-founded Stack Overflow with Joel Spolsky in 2008). You can read every line of the source on GitHub, fork it, modify it, run it on your own server with a single docker run command, and export every Topic and every reply as a Postgres dump or a JSON archive any time you want. Discourse the company sells hosted plans (Discourse-on-server) starting around USD 100 per month, which is the right call if you do not want to run a Rails app and a Postgres database yourself. But the software is the same software whether you self-host or pay Discourse to host it for you, which means a third-party widget like Poper works identically on both. The corporate forum alternatives are a different story. Circle.so is a closed SaaS at USD 89 per month minimum, your data is hostage to your subscription, and the embed surface is a screenshot script that breaks if you cancel. Slack Communities are even worse: messages older than 90 days are inaccessible on free plans, and you cannot embed Slack content on a public website at all. Reddit is corporate, ad-supported, and locked the API behind a paid tier in 2023. Discourse stands alone as the serious open-web alternative, which is why open-source projects (the Rust language forum, the Cargo registry, the WordPress.org community), education programs (Recurse Center, freeCodeCamp), and brand-owned communities (Discourse itself, the Helium network, BoardGameGeek) all converged on it. The Poper widget is the natural embed surface for that ecosystem.