# Learn how to build Discourse plugins by helping me

**URL:** https://meta.discourse.org/t/learn-how-to-build-discourse-plugins-by-helping-me/87048
**Category:** Development
**Created:** [9 mei 2018 om 09:09 UTC](https://meta.discourse.org/t/learn-how-to-build-discourse-plugins-by-helping-me/87048 "2018-05-09T09:09:32Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![ryanerwin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ryanerwin/32/94589_2.png) [@ryanerwin](https://meta.discourse.org/u/ryanerwin)
#### Post date: [26 juli 2018 om 07:50 UTC](https://meta.discourse.org/t/learn-how-to-build-discourse-plugins-by-helping-me/87048/13 "2018-07-26T07:50:36Z")

</div>

For anyone on this topic that was interested in improving their plugin developing ability, I thought that a “newby discourse dev” category might be a useful tool. If you think so too, chime in:

> [@Channel for Informal Dev Chat?](https://meta.discourse.org/t/where-to-be-a-noisy-newby-discourse-developer/93179):
>
> There’s a big difference between catching the eye of a colleague that’s also got the “i’m stuck” expression on their face, and formulating a long, accurate, useful forum post that is worth the attention of senior developers. What do you think of a category with much less formal etiquette where newby Discourse developers can exchange ideas and crowd source their troubleshooting? questions don’t need to be “properly formulated” answers don’t need to be correct and/or tested no issue is “too sma…

---

_[View the full topic](https://meta.discourse.org/t/learn-how-to-build-discourse-plugins-by-helping-me/87048)._