# Developing plugins, Pinegrow reference

**URL:** <https://forum.pinegrow.com/t/developing-plugins-pinegrow-reference/965>\
**Category:** Third Party Plugins\
**Created:** [May 31, 2017, 2:19pm UTC](https://forum.pinegrow.com/t/developing-plugins-pinegrow-reference/965 "2017-05-31T14:19:58Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Pinegrow\_User](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/pinegrow_user/32/4919_2.png) [@Pinegrow\_User](https://forum.pinegrow.com/u/Pinegrow_User)\
**Post date:** [August 22, 2018, 2:43pm UTC](https://forum.pinegrow.com/t/developing-plugins-pinegrow-reference/965/6 "2018-08-22T14:43:02Z")

</div>

@matjaz, @Emmanuel, @MhdAljuboori, @pinegrowteam @pinetreeseverywhere

> > [@Prevent Files from being overwritten](https://forum.pinegrow.com/t/prevent-files-from-being-overwritten/2128/4):
> >
> > **a lot of trial and error** and looking at the frameworks bundled with PG for tips as **not much info in the docs**. Constant loading and unloading of Plugin to test.

The above comment in a recent thread, once again brings into question when we might be able to expect proper documentation for the “Pinegrow Plugin / Developer API” ?

\*\* Surely there must reside somewhere internally documentation or at least full code comments from when it was initially developed and implemented? ;–)

Discussion of providing proper documentation has been mentioned for some time:

* * *

> > > More documentation will be available soon. —— February 15 2017
> 
> ![February%2015%202017](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/b/bac1102456be2c877ae8dfa6bd5e0e28053cfcc4.png)
> 
> > > We’ll do more for plugin developers once we clear all the PG3 bugs. —— July 7th 2017
> 
> ![July%207th%202017](https://canada1.discourse-cdn.com/flex036/uploads/pinegrow/original/2X/1/1aa603b1b94a214fed1cf126f28186c5a6b36100.png)

* * *

Another year has passed, and PG5 is now on the horizon.

I’m sure many have looked through all the available information, plugins, along with the files in the Pinegrow App Bundle itself. Yet so much is still vague as you try to piece together and trace the purpose, all the available function calls, events, properties, etc.

Please provide us with a complete and proper API listing and documentation. No doubt many would love to develop and add more plugins and features to Pinegrow if they were only better equipped to do so.

\*\* Doesn’t something already reside internally?

**Thank you.**

🌲 ♥ 😉

---

_[View the full topic](https://forum.pinegrow.com/t/developing-plugins-pinegrow-reference/965)._