Discourse Forum Plugins List – All Working Discourse Plugins
Best Discourse Plugins Worth Using Right Now
If you’re trying to figure out which Discourse plugins still deserve a spot on a live forum, this is the short version. I cut the dead weight, kept the stuff that still solves real problems, and called out the plugins I’d install only with caution. If you run support, events, moderation, or reporting, you’ll leave with a practical shortlist instead of a giant pile of dusty repos.
One rainy evening, I was cleaning up an old Discourse install and opened a bookmarks folder full of plugin links from years back. Half were abandoned. A few had basically been replaced by core Discourse features. And some still worked, but felt like relics from a different version of the internet. That’s the problem with plugin roundups, they rot fast.
So I rewrote this properly. This is a trimmed, current-minded list, not a museum of random repos. And yes, before you install anything, ask the boring question first. Do you need this feature, or are you just signing yourself up for update pain later?
If you’re new to Discourse, here’s the big shift since older plugin lists were written. A lot of features that once needed third-party plugins now live in core, official plugins, or theme components. So the smart move in 2026 is usually fewer plugins, not more.
01Quick comparison of useful Discourse plugins
| Plugin | What it does | Status | Best for |
|---|---|---|---|
| Discourse Events | Adds events and date-based topic scheduling | Still useful | Communities running meetups, launches, live sessions |
| Discourse Locations | Adds topic locations and map-based views | Niche but useful | Local groups, travel, regional communities |
| Discourse Solved | Marks replies as accepted solutions | Essential | Support forums and product communities |
| Discourse Question Answer | Adds Stack Overflow style voting and Q&A behavior | Use carefully | Technical communities that need ranked answers |
| Discourse Whos Online | Shows active users currently online | Still active in many setups | Community-heavy forums that want visible activity |
| Discourse Spoiler Alert | Blurs spoiler text and reveals on click | Still handy | TV, movies, gaming communities |
| Discourse Canned Replies | Saves reply templates for moderators and support staff | Very useful | Support desks and moderation teams |
| Discourse Ads | Adds ad placements in forums | Check current support first | Ad-supported communities |
| Discourse Data Explorer | Lets admins run SQL queries on forum data | Excellent | Admins who want real reporting |
| Discourse Chat Integration | Sends post alerts to Slack, Discord and others | Still useful | Teams managing active communities |
02Essential Discourse plugins I’d start with
If I had to set up a Discourse forum today, I would not install twenty plugins because some old blog said I should. I’d start with the plugins that solve obvious pain. Most forums need support workflow, moderation help, better reporting, and maybe one UX upgrade. That’s enough for day one.
- Discourse Solved
- Discourse Canned Replies
- Discourse Data Explorer
- Discourse Chat Integration
- Discourse Events
- Topic Preview
- Discourse Whos Online
03Functionality related plugins
1. Discourse Events

Caption: The Events plugin turns a normal topic into something people can actually use for scheduling.
I still like this one. If your community runs webinars, office hours, game nights, launches, or local meetups, this plugin gives those threads some structure. Dates stop getting buried in a wall of text, and people can follow an event without doing detective work in the replies.
| Key fact | Details |
|---|---|
| Use case | Event topics with date and time ranges |
| Works well for | Meetups, launches, office hours, webinars |
| Maintenance note | Check current compatibility with your Discourse version before install |
| Repo | https://github.com/angusmcleod/discourse-events |
Best for: Forums that host recurring events.
Skip if: Your calendar already lives elsewhere and nobody uses event threads anyway.
2. Location Plugin

Caption: Category-level location settings help keep map features limited to the areas that need them.

Caption: Topics can be shown on a map instead of just another flat list.
This one is niche, but when it fits, it fits properly. If your forum is about local services, real estate, travel, hiking spots, or regional meetups, map-aware topics are genuinely useful. If not, it just adds clutter to the composer and gives admins one more thing to maintain.
I’ve seen people install location features because screenshots looked cool. Then nobody uses them after the first week. That part is painfully common.

Caption: A mini-map inside the topic helps readers confirm the place without leaving the thread.
| Key fact | Details |
|---|---|
| Use case | Add topic locations and map views by category |
| Works well for | Regional communities, travel, local marketplaces |
| Hidden cost | Map and geocoding setup adds complexity fast |
| Repo | https://github.com/angusmcleod/discourse-locations |
Best for: Local-first communities.
Skip if: Your members are global and location barely matters in discussion.
3. Election Plugin

Caption: The Elections plugin adds nomination and voting flow on top of standard polls.
This plugin builds on Discourse polls and adds a more formal election workflow. So if you run moderator elections, council seats, or member reps, it gives you a cleaner process than hacking it together in a topic. For governance-heavy communities, that’s useful.
My honest take, most forums don’t need it. They imagine they’ll run neat democratic processes and then end up with three nominees, low turnout, and one awkward announcement thread on a humid Sunday night.

Caption: Election controls live inside the topic, which keeps the process in one place.
| Key fact | Details |
|---|---|
| Use case | Structured community elections |
| Built on | Discourse Polls |
| Works well for | Open-source communities, member-run forums |
| Repo | https://github.com/angusmcleod/discourse-elections |
Best for: Communities with real governance needs.
Skip if: You just need a normal poll and a sensible moderation team.
4. Discourse Question Answer

Caption: This plugin pushes Discourse closer to a Q&A layout with ranked answers.
This plugin tries to make Discourse behave more like Stack Overflow. Users can vote, stronger answers rise, and threads become more answer-focused than conversational. For technical forums, that can work really well.
I used to recommend this harder. I don’t anymore. A lot of communities think they want strict Q&A, but their real value comes from discussion, nuance, and back-and-forth. If you force every thread into ranked-answer mode, you can flatten the part that makes a forum feel human.
| Key fact | Details |
|---|---|
| Use case | Stack Overflow style Q&A threads |
| Main feature | Voting on answers and question-style layout |
| Warning | Can make general discussion feel too rigid |
| Repo | https://github.com/angusmcleod/discourse-question-answer |
Best for: Dev forums and support communities with repeat technical questions.
Skip if: Your users come to talk things through, not just post accepted answers.
5. Discourse Solved Plugin
If your forum handles support, this is the one I’d install before almost everything else. It lets the topic owner or staff mark a reply as the accepted solution, and that saves everyone time. Simple feature. Big payoff.
I’ve seen support forums full of threads that ended with “fixed it” or “never mind” and no marked answer anywhere. That’s a waste of reader patience. Solved status cleans that mess up fast.
| Key fact | Details |
|---|---|
| Use case | Mark accepted answers in support topics |
| Works well for | Customer support, product forums, help desks |
| Status | One of the most practical Discourse add-ons |
| Repo | https://github.com/discourse/discourse-solved |
Best for: Any forum where people ask for help.
Skip if: Your community is purely social and nobody is trying to solve anything.
6. Topic Rating Plugin

Caption: Star ratings can help surface stronger replies, but only if your members actually use them.
This plugin lets users rate replies with stars. Sounds good on paper. In practice, it depends a lot on your audience. On a niche expert forum, ratings can help sort useful replies from average ones. On a casual community, it’s often just extra noise.
| Key fact | Details |
|---|---|
| Use case | Rate replies inside topics |
| Works well for | Expert communities, Q&A-heavy forums |
| Warning | Low-engagement communities may ignore it completely |
| Repo | https://github.com/angusmcleod/discourse-ratings |
Best for: Forums where answer quality varies a lot.
Skip if: Your members barely use likes. They probably won’t rate replies either.
04Utility plugins
1. Discourse Whos Online Plugin

Caption: A visible online-user bar can make a busy forum feel alive at a glance.
I have mixed feelings about this one, but I still think it earns a place on the right forum. Showing active users can make the place feel alive, and that helps with social proof when a new visitor lands. You want them to feel like somebody’s home.
But if your forum is quiet, this plugin can snitch on you. Nothing sadder than a “Who’s Online” block showing the same two moderators and one bot.
| Key fact | Details |
|---|---|
| Use case | Display active users currently online |
| Works well for | Busy forums and active communities |
| Warning | Can highlight low traffic if your forum is small |
| Repo | https://github.com/davidtaylorhq/discourse-whos-online |
Best for: Communities with steady daily activity.
Skip if: Your traffic is still tiny and you’d rather not put that on display.
2. Spoiler Alert

Caption: Spoiler formatting is simple, clear, and people understand it instantly.
If you run a forum about movies, anime, books, TV, or games, this is one of those easy wins. Users can wrap content in tags and the text stays blurred until clicked.
That’s really it. No learning curve. No weird workflow. It just works, which is rarer than it should be.
| Key fact | Details |
|---|---|
| Use case | Hide spoiler content behind click-to-reveal blur |
| Works well for | Entertainment and gaming communities |
| Input format | ... |
| Repo | https://github.com/discourse/discourse-spoiler-alert |
Best for: Fan communities.
Skip if: Nobody on your forum discusses plot-heavy content.
3. Image Gallery Plugin

Caption: Gallery formatting helps when members post image sets instead of one-off screenshots.
If your community shares lots of photo sets, portfolio work, tutorials, or before-and-after images, gallery formatting can clean things up nicely. On a text-first forum, though, this is an easy thing to skip.
| Key fact | Details |
|---|---|
| Use case | Turn multiple images into gallery layouts |
| Works well for | Photography, design, hobby and showcase forums |
| Warning | May not be worth the maintenance for text-first communities |
| Repo | https://github.com/crob611/discourse-image-gallery |
Best for: Visual communities.
Skip if: Images are occasional and not central to the forum.
4. Twitter Profile Link
This made more sense in the old Twitter era. In 2026, I’d treat it as borderline legacy unless your community still uses X or Twitter identity in a real way. Social login habits changed, branding changed, and plenty of communities moved on.
I couldn’t confirm this as a recommendation I’d publish without checking your current auth stack first. Consider this one stale unless you have a very specific reason.
| Key fact | Details |
|---|---|
| Use case | Adds a Twitter profile link for users authenticated through Twitter |
| Status note | Potentially stale depending on current authentication support |
| Repo | https://github.com/discourse/twitter-profile-link |
Best for: Communities still tied to Twitter-based identity.
Skip if: You don’t use Twitter login, or your audience simply does not care anymore.
5. Discourse Canned Replies

Caption: Saved replies look boring until your team answers the same thing all week.

Caption: Templates can be inserted from the composer, which saves moderators real time.
This is one of those plugins that never looks exciting in screenshots, then becomes very hard to live without once your forum grows. Mods and support staff repeat the same instructions all day. Saved replies fix that and keep answers consistent.
I’ve used canned responses in support systems outside forums too. The relief is real. You still tweak the wording sometimes, but you’re not retyping the same fix ten times before lunch.
| Key fact | Details |
|---|---|
| Use case | Save and insert reusable replies |
| Works well for | Support teams, moderators, onboarding workflows |
| Hidden detail | You may still need to tailor context before sending |
| Repo | https://github.com/discourse/discourse-canned-replies |
Best for: Forums with repeated support questions.
Skip if: Your staff replies are low-volume and always custom.
6. Autobot, Auto Content Generator
I’m keeping this here mostly as a warning. Pulling content from RSS, YouTube, or social feeds can make a forum look busy for a week, but it often creates a dead-feeling place full of imported posts nobody owns. And search engines are not stupid about this anymore.
If you use this at all, use it only for your own content. Like syncing your own blog posts into your own forum. Anything beyond that starts smelling spammy very quickly, and honestly, readers can feel it too.
| Key fact | Details |
|---|---|
| Use case | Auto-post content from feeds and channels |
| Main risk | Low-value content and search quality problems |
| Safer use | Syncing your own content only |
| Repo | https://github.com/vinkashq/discourse-autobot |
Best for: Limited internal syndication.
Skip if: You were planning to grow a community by scraping everybody else’s content. Bad plan, yaar.
7. Extra Button For Specific Groups

Caption: A custom button can help staff or paid members complete one specific action faster.
This is a small plugin, and small plugins can be surprisingly helpful. If you need a visible action for staff, premium members, or one specific user group, adding a targeted button can make the workflow cleaner.
| Key fact | Details |
|---|---|
| Use case | Add a custom button visible to specific groups |
| Works well for | Staff tools, premium actions, custom workflows |
| Repo | https://github.com/discourse/discourse-topic-group-button |
Best for: Forums with custom member flows.
Skip if: You don’t already know exactly what the button should do.
8. Category Moderator
This helps moderators focus on specific categories instead of spreading everybody across the whole forum. That makes sense on larger communities where one mod handles support, another handles feedback, and somebody else deals with off-topic nonsense at 1 a.m.
| Key fact | Details |
|---|---|
| Use case | Category-specific moderation workflow |
| Works well for | Large forums with distributed moderation teams |
| Repo | https://github.com/angusmcleod/discourse-category-moderator-lite |
Best for: Bigger communities with clear role separation.
Skip if: You have one or two moderators doing everything anyway.
9. Babble Chat Plugin

Caption: Chat can increase engagement, but it can also pull useful discussion away from searchable topics.
Back in the day, this was a common way to bolt chat onto Discourse. Today, I’d be careful. Discourse itself has stronger chat support than it used to, so Babble is no longer the obvious answer it once was.
This is one of those plugins that solved a real gap years ago. That gap is smaller now. So compare it against native or official chat options before you commit.
| Key fact | Details |
|---|---|
| Use case | Adds chat channels alongside forum discussion |
| Main trade-off | More engagement, less searchable long-form content |
| Status note | Compare with current native Discourse chat before using |
| Repo | https://github.com/gdpelican/babble |
Best for: Communities that genuinely need live chat.
Skip if: You want your forum content to stay searchable and useful months later.
05Financial plugins
1. Discourse Adsense
Monetizing a forum with ads sounds easy until you actually do it. The plugin can place ads in sensible spots, sure, but the bigger question is whether ads are worth the user experience hit. On some communities, yes. On others, the whole place starts feeling cheap very fast.
Also, ad support and policy compliance change. So check current repo activity and your ad network’s rules before relying on this in 2026.
| Key fact | Details |
|---|---|
| Use case | Insert ad placements into Discourse |
| Works well for | Large, ad-supported communities |
| Warning | Current support and policy compatibility should be verified |
| Repo | https://github.com/discoursehosting/discourse-adsense |
Best for: Forums with real traffic and a clear ad strategy.
Skip if: You’re trying to monetize a tiny community too early.
2. Stripe Donations
If your forum has loyal members and gives them real value, donations can work. Stripe-based donation tools are cleaner than duct-taping random payment buttons into your sidebar. But country support matters, and if you’ve ever tried building payments from Pakistan or other unsupported regions, you already know the headache.
I couldn’t confirm this exact plugin as the best current path, so I’d verify its maintenance status before publishing it as a live recommendation. The need is still real. The plugin choice may have changed.
| Key fact | Details |
|---|---|
| Use case | Collect community donations via Stripe |
| Works well for | Member-supported forums |
| Warning | Stripe country availability and plugin maintenance need checking |
| Repo | https://github.com/choiceaustralia/discourse-donations |
Best for: Niche communities with loyal members.
Skip if: Your payment stack is already giving you a migraine.
06Themes and styling
1. Messages Icon and Box
This adds a dropdown-style private message experience in the header. Nice idea if your members use PMs a lot and want a more chat-like flow. If they don’t, it’s just another thing in the header fighting for attention.
| Key fact | Details |
|---|---|
| Use case | Improves visibility and access for private messages |
| Works well for | Communities that use PMs heavily |
| Repo | https://github.com/angusmcleod/discourse-quick-messages |
Best for: Forums with active member-to-member messaging.
Skip if: PMs are barely touched.
2. Discourse National Flags Plugin

Caption: Country flags can make a global forum feel a bit more human and easier to scan.

Caption: Flags help readers quickly understand where members are posting from.
I like this one on international communities. It adds personality, and it gives useful context on forums where laws, prices, shipping, or services differ by country. On the wrong forum though, location can be sensitive, so use some sense.
| Key fact | Details |
|---|---|
| Use case | Show member country flags |
| Works well for | International communities |
| Input | Users manually choose their country |
| Repo | https://github.com/Ebsy/discourse-nationalflags |
Best for: Forums with a global user base.
Skip if: Location is sensitive or irrelevant to your members.
3. Discourse Awesome BBcodes
If you’re migrating users from older forum software, BBCode support can reduce a lot of silly complaints. People get emotionally attached to old posting habits in a way that makes no logical sense, but there it is.
,- Typeface tags like
,,,,
| Key fact | Details |
|---|---|
| Use case | Add BBCode-style tags to Discourse |
| Works well for | Migrations from vBulletin and older forum systems |
| Repo | https://github.com/rux-pizza/discourse-awesome-bbcodes |
Best for: Communities moving from legacy forums.
Skip if: Your users are already fine with normal Discourse formatting.
4. Discourse MathJax

Caption: MathJax makes formula-heavy posts readable instead of painful.
If your forum covers math, physics, engineering, economics, or anything education-heavy, this is a strong add-on. Formula support sounds optional until somebody tries to explain calculus in plain text and the whole thread turns into soup.
| Key fact | Details |
|---|---|
| Use case | Render mathematical notation in posts |
| Works well for | Academic and technical communities |
| Repo | https://github.com/kasperpeulen/discourse-mathjax |
Best for: STEM forums.
Skip if: Your users will never post equations.
5. Discourse Tooltip

Caption: Hover previews can save readers from opening ten vague thread titles in a row.
This plugin shows a topic excerpt on hover. Tiny feature, nice effect. If your forum has vague titles or lots of similar support threads, hover previews help people scan faster without opening everything.
| Key fact | Details |
|---|---|
| Use case | Show topic excerpts on hover |
| Works well for | Busy forums with dense topic lists |
| Repo | https://github.com/discourse/discourse-tooltips |
Best for: Content-heavy forums.
Skip if: Your theme or mobile-heavy audience makes hover behavior less useful.
6. Discourse Topic Preview
![]()
Caption: Topic previews make the homepage feel more visual and less like a plain list of threads.
This one makes Discourse feel a bit more magazine-like. It can show excerpts and thumbnails beside topic titles, which works well for visual communities, creator spaces, and media-heavy forums. On a support forum, I’d be less excited.
| Key fact | Details |
|---|---|
| Use case | Show excerpts and thumbnails in topic lists |
| Works well for | Visual communities and content-driven forums |
| Repo | https://github.com/angusmcleod/discourse-topic-previews |
Best for: Forums where post imagery matters.
Skip if: Your community is mostly text and support threads.
7. Custom Wizard

Caption: Wizards help when new users need setup guidance, not just a welcome message.
I’m a fan of guided onboarding when it solves a real problem. If users need to choose a role, join specific groups, accept rules, or complete setup before posting, custom wizards can help a lot.
If your forum is simple though, don’t overdo it. Nobody wants to answer five setup screens just to ask one question.
| Key fact | Details |
|---|---|
| Use case | Create custom onboarding or workflow wizards |
| Works well for | Complex communities and membership flows |
| Repo | https://github.com/angusmcleod/discourse-custom-wizard |
Best for: Structured communities with onboarding needs.
Skip if: You just want a normal forum signup.
8. Layout Plugin

Caption: Sidebars are only useful if you have something genuinely worth putting there.
This plugin adds sidebar-style layout options. For some communities, that’s handy. You might want announcements, sponsor blocks, quick links, or category-specific widgets. For others, it just drags Discourse back toward the clutter older forums never escaped.
| Key fact | Details |
|---|---|
| Use case | Add sidebars and custom layout regions |
| Works well for | Forums with extra navigation or sponsor content |
| Warning | Can make a clean interface feel crowded |
| Repo | https://github.com/angusmcleod/discourse-layouts |
Best for: Communities with intentional sidebar content.
Skip if: You’re adding widgets just because old-school forums had widgets.
9. Header Visible Search

Caption: A visible search bar can nudge users to search before posting duplicate threads.
This is one of those small UX tweaks I genuinely like. Making search visible in the header can encourage users to search before posting, especially on support forums where repeated questions never seem to die.
| Key fact | Details |
|---|---|
| Use case | Keep search visible in the desktop header |
| Works well for | Support forums and documentation-heavy communities |
| Device note | Desktop-focused behavior |
| Repo | https://github.com/angusmcleod/discourse-header-search |
Best for: Forums where search matters.
Skip if: Your theme already handles search well.
07Data related plugins
Admin Statistics

Caption: A simple stats view helps admins spot growth, drop-offs, and quiet categories faster.
I like any tool that helps admins stop guessing. Monthly reports can be useful if you’re tracking growth, engagement dips, or category performance. Just make sure this adds something beyond your current admin dashboard, because Discourse reporting has improved over time.
| Key fact | Details |
|---|---|
| Use case | Monthly overview of forum activity and trends |
| Works well for | Admins who want simple reporting |
| Repo | https://meta.discourse.org/t/admin-statistics-report/50943 |
Best for: Admins who want quick visibility.
Skip if: You already use deeper analytics elsewhere.
Discourse Database Explorer

Caption: Data Explorer is where you go when the normal dashboard stops answering the real questions.
This is easily one of the most useful admin tools in the whole Discourse world. If you know SQL, or can borrow a good query from someone who does, Data Explorer gives you real visibility into your forum. Retention, unanswered topics, moderator workload, trust-level trends, category growth, all the stuff that matters once the forum is no longer tiny.
Do one thing before running old queries from random Meta threads. Read them properly. Some are outdated, some are inefficient, and some answer a question you don’t even have.
| Key fact | Details |
|---|---|
| Use case | Run custom SQL queries on forum data |
| Works well for | Advanced reporting and business insight |
| Warning | Best used by admins comfortable with SQL |
| Repo | https://github.com/discourse/discourse-data-explorer |
Best for: Power users and admins who want real numbers.
Skip if: You’ll never open a query window.
08Third-party and integration plugins
1. Chat Notifications Integrations
This lets you push Discourse activity into Slack, Discord, and similar tools. For small teams, that’s actually useful. Mods see flagged posts faster, staff sees important mentions faster, and your forum feels connected to the rest of your workflow instead of living on an island.
| Key fact | Details |
|---|---|
| Use case | Send Discourse notifications to team chat tools |
| Works well for | Moderation teams and support operations |
| Repo | https://github.com/discourse/discourse-chat-integration |
Best for: Teams managing active communities.
Skip if: You don’t want one more source of notifications ruining your afternoon.
2. Marvelapp OneBox
This plugin was built for embedding Marvel prototypes. The obvious problem is that plenty of design teams don’t use Marvel anymore. Most have moved to Figma or other tools, so this feels very niche now.
| Key fact | Details |
|---|---|
| Use case | Embed Marvel prototypes in forum posts |
| Status note | Niche, and may be less relevant now depending on your design stack |
| Repo | https://github.com/naveed-ahmad/marvelapp_onebox |
Best for: Teams still using Marvel.
Skip if: Your design workflow moved on years ago.
3. Discourse Calendar Plugin

Caption: Calendar embeds are helpful when your community depends on a shared visible schedule.
This plugin embeds Google Calendar in a forum post. Useful if your community revolves around class schedules, public calendars, or visible event planning. But if you’re already using the Events plugin, you may not need both. That’s a common mistake.
| Key fact | Details |
|---|---|
| Use case | Embed Google Calendar inside topics |
| Works well for | Communities sharing public schedules |
| Repo | https://github.com/tcreativo/plugin_discourse_calendar |
Best for: Class schedules and public calendars.
Skip if: Event topics already cover what you need.
4. New Relic For Discourse
If you already use New Relic, this can help tie your forum into the rest of your monitoring setup. If you don’t, this is probably overkill. Most small forum owners do not need this level of application monitoring unless they enjoy turning everything into a DevOps side quest.
| Key fact | Details |
|---|---|
| Use case | Connect Discourse to New Relic monitoring |
| Works well for | Larger operations with an existing observability setup |
| Repo | https://github.com/davidcelis/new_relic-discourse |
Best for: Teams already using New Relic.
Skip if: You just want your forum to work quietly.
5. UML YUML Plugin

Caption: UML support can help in technical communities that explain systems visually.
This lets users share UML diagrams through the YUML service. Good fit for software architecture discussions, engineering topics, and technical education communities. Less useful almost everywhere else.
| Key fact | Details |
|---|---|
| Use case | Render UML diagrams using YUML |
| Works well for | Software, engineering and education forums |
| Warning | Relies on an external service, so check current availability first |
| Repo | https://github.com/sekhat/discourse-yuml |
Best for: Technical diagram-heavy communities.
Skip if: Your users never post architecture diagrams.
6. VK Login Integration
This adds VK login, which only matters if you have a meaningful Russian-speaking audience or a region-specific reason to support it. Otherwise, don’t bother. Also check current login support before you publish this as a live recommendation.
| Key fact | Details |
|---|---|
| Use case | Add VK social login |
| Works well for | Communities with Russian-speaking users |
| Repo | https://meta.discourse.org/t/vk-com-login-vkontakte/12987 |
Best for: Region-specific communities that need VK.
Skip if: Your audience has no reason to use it.
09Plugins I would treat carefully
Some plugins from older Discourse lists are still interesting, but I would not install them blindly now.
- Babble Chat, because native Discourse chat is much better than it used to be.
- Twitter Profile Link, because its relevance is shaky now.
- Stripe Donations, because payment plugins need current maintenance checks.
- Marvelapp OneBox, because many teams do not use Marvel anymore.
- Autobot, because lazy content automation can hurt the whole forum.
Common mistake: installing plugins because they look nice in screenshots. The real cost is not the install. It’s upgrades, theme conflicts, repo abandonment, debugging, and that one bizarre thing that breaks after a Discourse update when you’re already tired.
10Built-in or official features to check first
Some things that used to need extra plugins are now handled better by core Discourse or official components. Before you install anything, check your current version first.
- Push notifications
- Polls
- Chat features
- Basic reactions and emoji tools
- Theme components that replace older styling plugins
11How to install a plugin in Discourse
If you’ve mostly used WordPress, Discourse plugin installation feels a bit old-school. Usually you add the plugin repo to your container config and rebuild the app. Not difficult. Just less clicky.
You need SSH access and the plugin Git URL. And back up first. Seriously.
- Open Terminal on Mac or Command Prompt on Windows.
- SSH into your server with a command like
ssh username@your-server-ip. - If this is your first login, accept the security prompt.
- Enter your server password.
- Go to your Discourse folder with
cd /var/discourse. - Open the container config file with
nano containers/app.yml. - Find the section where plugin Git URLs are listed.
- Add your plugin repo URL on a new line in the same format as the others.
- Save the file and exit Nano.
- Rebuild Discourse with:
git pull
./launcher rebuild app
Wait for the rebuild to finish. If all goes well, the plugin should appear in your Discourse admin area after the container comes back up.
A small workaround I use, if I already know I need multiple plugins, I add them in one go. Rebuilding over and over is just a waste of time.
12What I’d actually install on a real forum
If it was my money and my forum, I’d start lean.
My starter stack: Discourse Solved, Canned Replies, Data Explorer, Chat Integration, and either Topic Preview or Whos Online depending on the kind of community. If I ran events, I’d add Events too. Everything else would need to prove itself first.
That’s the honest answer. Not thirty plugins. Five or six, max, until the community proves it needs more.
13Final recommendation
If you only install one plugin from this list, make it Discourse Solved for support forums. If you’re running a larger community and care about admin insight, make your second pick Discourse Data Explorer. Those two give the biggest practical return with the least nonsense.
If it were my forum, I’d start there, then add Canned Replies next. I’d avoid stuffing the forum with every shiny add-on from old directories. Start with pain points, not features. Future you will be grateful on some grey night when the server is moody and one random update doesn’t break fifteen things at once.
That’s the list I’d trust today.