# Plugin repo

**URL:** <https://discourse.joplinapp.org/t/plugin-repo/3986>\
**Category:** Features\
**Created:** [19 October 2019 14:56 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986 "2019-10-19T14:56:30Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![simo3o](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/simo3o/32/1586_2.png) [@simo3o](https://discourse.joplinapp.org/u/simo3o)\
**Post date:** [19 October 2019 14:56 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/1 "2019-10-19T14:56:30Z")

</div>

Would it be possible to implement a plugin repo as sublime/atom have, so “anyone” can upload themes and plugins to extend the functionality further?  
I think it would help make it even better.

---

<div class="post-metadata">

**Author:** ![tessus](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/tessus/32/13_2.png) [@tessus](https://discourse.joplinapp.org/u/tessus)\
**Post date:** [19 October 2019 23:45 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/2 "2019-10-19T23:45:36Z")

</div>

I’ve suggested the same thing a while back. I’m afraid such a plugin system might not be that easy to implement.

---

<div class="post-metadata">

**Author:** ![simo3o](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/simo3o/32/1586_2.png) [@simo3o](https://discourse.joplinapp.org/u/simo3o)\
**Post date:** [20 October 2019 06:40 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/3 "2019-10-20T06:40:39Z")

</div>

I think it’d make joplin a lot more popular and a lot more functional and it would make focus the efforts on the base functionality of the app rather than trying to extend it because that would be done via plugins. I like how qownnotes has its script repo for example.

---

<div class="post-metadata">

**Author:** ![tessus](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/tessus/32/13_2.png) [@tessus](https://discourse.joplinapp.org/u/tessus)\
**Post date:** [20 October 2019 07:04 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/4 "2019-10-20T07:04:10Z")

</div>

I’m not disagreeing with you. I’m just saying that there are more pressing issues on the list right now. I can only hope and wish that such a plugin system will be part of Joplin at one point in the future.

---

<div class="post-metadata">

**Author:** ![talkdirty](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/talkdirty/32/1872_2.png) [@talkdirty](https://discourse.joplinapp.org/u/talkdirty)\
**Post date:** [4 November 2019 15:32 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/5 "2019-11-04T15:32:20Z")

</div>

I have to agree with simo3o! I started using Joplin recently and I love it, except for the fact that it feels quite confined in what you’re allowed to do with your notes.  
@tessus is right in saying that a fully fledged plugin system would probably be quite a lot of effort to implement. It could however save effort in the long run by empowering the community to contribute features that are not suited for everyone as it might be a niche use-case, etc.

That said, I think a “MVP” in plugin support would be a configuration switch to allow custom JS in the Notes section. That would allow “power-users” to do a lot, while being quite easy to implement (I think anyway!), as the Notes section is just a Electron rendered Webpage anyway.

---

<div class="post-metadata">

**Author:** ![simo3o](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/simo3o/32/1586_2.png) [@simo3o](https://discourse.joplinapp.org/u/simo3o)\
**Post date:** [12 November 2019 16:54 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/6 "2019-11-12T16:54:16Z")

</div>

That’s a good idea, just by enabling JS in a script tag would open a lot of possibilities.

---

<div class="post-metadata">

**Author:** ![tessus](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/tessus/32/13_2.png) [@tessus](https://discourse.joplinapp.org/u/tessus)\
**Post date:** [12 November 2019 17:39 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/7 "2019-11-12T17:39:26Z")

</div>

> [@simo3o](#):
>
> would open a lot of possibilities.

or the proverbial can of worms....

---

<div class="post-metadata">

**Author:** ![rami.sedhom](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/rami.sedhom/32/1894_2.png) [@rami.sedhom](https://discourse.joplinapp.org/u/rami.sedhom)\
**Post date:** [26 December 2019 14:12 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/10 "2019-12-26T14:12:35Z")

</div>

I second @simo3o having plugin systems as mid/long term, and may be start with enabling JS as @talkdirty suggest

---

<div class="post-metadata">

**Author:** ![psophos](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/psophos/32/1954_2.png) [@psophos](https://discourse.joplinapp.org/u/psophos)\
**Post date:** [26 December 2019 15:06 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/11 "2019-12-26T15:06:09Z")

</div>

could we imagine a cloud of tags for instance ?  
Or an OCR plugin to search for words in picts ?

Whaaaaaaa

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [12 January 2020 13:37 UTC](https://discourse.joplinapp.org/t/plugin-repo/3986/12 "2020-01-12T13:37:01Z")

</div>

Perhaps we got to a point where the Joplin core applications already has all the main features, and new stuff should be developed as plugins.