# Embedding discussions in plugins.jenkins.io

**URL:** <https://community.jenkins.io/t/embedding-discussions-in-plugins-jenkins-io/140>\
**Category:** Site Feedback\
**Created:** [June 17, 2021, 12:10am UTC](https://community.jenkins.io/t/embedding-discussions-in-plugins-jenkins-io/140 "2021-06-17T00:10:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![oleg-nenashev](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/oleg-nenashev/32/36_2.png) [@oleg-nenashev](https://community.jenkins.io/u/oleg-nenashev)\
**Post date:** [June 17, 2021, 12:10am UTC](https://community.jenkins.io/t/embedding-discussions-in-plugins-jenkins-io/140/1 "2021-06-17T00:10:00Z")

</div>

Jenkins Wiki had support for comments. It was quite handy for plugins, because users were able to discuss the plugins right inside the page. It was not a good channel for support and issue reporting though…

What if we allow doing the same on [https://plugins.jenkins.io/](https://plugins.jenkins.io/) ?

- There is a new “Plugins” category created in Discourse, e.g. as a Using Jenkins sub-category
- Discourse embedding is configured as recommended in [Embedding Discourse Comments via Javascript - developers - Discourse Meta](https://meta.discourse.org/t/embedding-discourse-comments-via-javascript/31963), with automatic creating of topics on-demand (“Plugins” category). Note that it is different from [Embedding discussions into jenkins.io](https://community.jenkins.io/t/embedding-discussions-into-jenkins-io/139) settings ATM
- There is a new “Discuss” tab on the plugins site. This tab provides a “Not an issue tracker” disclaimer and then embeds the Discourse conversation

---

<div class="post-metadata">

**Author:** ![oleg-nenashev](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/oleg-nenashev/32/36_2.png) [@oleg-nenashev](https://community.jenkins.io/u/oleg-nenashev)\
**Post date:** [June 17, 2021, 12:10am UTC](https://community.jenkins.io/t/embedding-discussions-in-plugins-jenkins-io/140/2 "2021-06-17T00:10:42Z")

</div>

If @halkeye @timja @zbynek @olblak agree in principle, I will be happy to prototype this integration

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [June 17, 2021, 12:30am UTC](https://community.jenkins.io/t/embedding-discussions-in-plugins-jenkins-io/140/3 "2021-06-17T00:30:24Z")

</div>

No thank you. Plugin site already gets a bunch of tickets open for plugin support. I didn’t like the comments on the wiki and often found them outdated out not useful

---

<div class="post-metadata">

**Author:** ![timja](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/timja/32/7_2.png) [@timja](https://community.jenkins.io/u/timja)\
**Post date:** [June 17, 2021, 6:49am UTC](https://community.jenkins.io/t/embedding-discussions-in-plugins-jenkins-io/140/4 "2021-06-17T06:49:42Z")

</div>

Agree with Halkeye, the comments on the wiki were not useful to me, often horribly outdates and were in general support issues and it wasn’t monitored as such.

More appropriate forums should be used, issue tracker or discussion channels

There _could_ be a link pointing to somewhere to create a discussion, but not something like a comment, the information required just wouldn’t be there