# Getting the most out of the Wordpress plugin

**URL:** https://meta.discourse.org/t/getting-the-most-out-of-the-wordpress-plugin/364492
**Category:** WordPress
**Created:** [May 2, 2025, 8:07am UTC](https://meta.discourse.org/t/getting-the-most-out-of-the-wordpress-plugin/364492 "2025-05-02T08:07:14Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [May 7, 2025, 5:59am UTC](https://meta.discourse.org/t/getting-the-most-out-of-the-wordpress-plugin/364492/4 "2025-05-07T05:59:15Z")

</div>

I would second what Maiki said, and add that the way I often explain this to folks is that you can think of Discourse comments in Wordpress as a way to entice people into your community. You likely want people to come across and spend time in your community itself. There are many wonderful and rich features of Discourse that will only ever be on the Discourse platform, even if two-way commenting (e.g. being able to compose a post in Wordpress) is ever possible.

That said, two-way commenting functionality has been discussed in more depth here:

> [@Should Discourse make an effort to become a viable comment platform?](https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-a-viable-comment-platform/274455/55):
>
> To be honest my biggest concern here is timing. Composer v2 is just around the corner, it would be crazy to embark on this adventure and not lean on our new composer but there is a mountain of work we need upfront to make using it in a lightweight app feasible. I think the right thing to do here is to watch this space for new composer for say 2-3 months and then revisit the question.

---

_[View the full topic](https://meta.discourse.org/t/getting-the-most-out-of-the-wordpress-plugin/364492)._
