# Introducing support and new resources for Pinegrow plugin developers

**URL:** <https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841>\
**Category:** Announcements\
**Created:** [March 5, 2020, 9:35am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841 "2020-03-05T09:35:12Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [March 5, 2020, 9:35am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/1 "2020-03-05T09:35:12Z")

</div>

Hi! I’m happy to announce that we launched a new [documentation portal](https://github.com/Pinegrow/PinegrowDevelopersDocumentation?__s=xxxxxxx) aimed at developers who wish to extend Pinegrow with their own frameworks and features.

And that’s not all.

We now also have a dedicated team member whose role is supporting our developer community - [Bob Means](https://forum.pinegrow.com/u/robm/summary?__s=xxxxxxx).

Bob has been an active member of our user community, and has been independently creating Pinegrow extensions and developer tutorials.

Welcome to the team, Bob!

# The pioneers of Pinegrow plugin development

From the very beginning Pinegrow was designed to be extendible. Most of its features are implemented as plugins that extend the core web editor, for example:

- Support for frameworks like Bootstrap, Foundation, and even Plain HTML projects,
- Components and master pages,
- Static HTML CMS,
- WordPress theme builder,
- Visual CSS Grid editor…

We always had the intention to let developers extend Pinegrow.

Although the API was always open and accessible, it was never properly documented and we didn’t manage to establish proper support for developers.

Despite that, a bunch of resourceful and brave enthusiasts did manage to dig into Pinegrow’s code, figure out how the API works, and develop their own extensions.

Here are some of the ones we know of:

- [Mohammed](https://forum.pinegrow.com/u/MhdAljuboori?__s=xxxxxxx) created [Animator and Animator Pro plugins](https://animator-pro.mhdaljuboori.me/?__s=xxxxxxx) for creating web animations. Soon after, this led to Mohammed joining our team.
- [Ben](https://forum.pinegrow.com/u/benhanna?__s=xxxxxxx) created a [huge collection](https://pluginsforpinegrow.com/?__s=xxxxxxx) of reusable blocks and a couple of plugins.
- [Thomas](https://forum.pinegrow.com/u/thomas?__s=xxxxxxx) implemented support for his custom framework Reginald.
- Bob created the plugin for [UIKit and responsive images](http://plugins.springhilldesign.net/pinegrow/?__s=xxxxxxx). Bob also thoroughly [documented](https://www.robertmeans.net/adding-uikit-to-pinegrow-pt-1/?__s=xxxxxxx) the process of building the UIKit framework.

# Resources for developers

At this, first, stage, we want to support developers who are interested in extending Pinegrow with new frameworks, workflows, tools and integrations.

- [Pinegrow Developers Documentation](https://github.com/Pinegrow/PinegrowDevelopersDocumentation?__s=xxxxxxx), a public GitHub repository with the first version of the API documentation.
- [Plugin Boilerplate](https://github.com/Pinegrow/PinegrowPluginQuickStartTemplate?__s=xxxxxxx), another GitHub repository with the boilerplate code for creating a feature-rich framework plugin.
- [Plugin Developers category on Pinegrow forum](https://forum.pinegrow.com/c/plugin-development/39?__s=xxxxxxx). That will be the main place for sharing information, answering questions and solving issues connected to developing Pinegrow extensions.

We’ll be adding new information and examples in response to needs expressed in the developer community.

The goal is to make development easier for existing developers and encourage others to join and create Pinegrow extensions, be it for their own needs, to integrate Pinegrow with workflows of their organizations or to create solutions aimed at the broad Pinegrow user base.

In the second stage we’ll work on making it easy to distribute and market such extensions within the Pinegrow community.

Looking forward to what we’ll create together!  
Matjaz

---

<div class="post-metadata">

**Author:** ![Thomas](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/thomas/32/61_2.png) [@Thomas](https://forum.pinegrow.com/u/Thomas)\
**Post date:** [March 5, 2020, 3:19pm UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/2 "2020-03-05T15:19:59Z")

</div>

Very - very cool guys @PG towers!

I’d first like to commend Bob @RobM who was the right man at the right time. I’m pretty sure, having a nice time together - and lot’s of questions and perhaps even a lil bit of help for him (if required).

> [@matjaz](#):
>
> [Thomas](https://forum.pinegrow.com/u/thomas?__s=xxxxxxx) implemented support for his custom framework Reginald.

Yipiehh - I am a pioneer - and still a lil bit proud of it!

In fact I know not much of programming and JavaScript at all. But thanks to the (at that time) existing MaterialDesign plugin and a very basic example, I was able to recreate my own “classifier”, still stunned that it works - and it does.

Looking forward to the upcoming.

Cheers

Thomas

---

<div class="post-metadata">

**Author:** ![matjaz](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/matjaz/32/5_2.png) [@matjaz](https://forum.pinegrow.com/u/matjaz)\
**Post date:** [March 6, 2020, 6:20am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/3 "2020-03-06T06:20:30Z")

</div>

Thanks @Thomas!

That’s an interesting point - it’s really quite simple to create a useful PG plugin.

---

<div class="post-metadata">

**Author:** ![Marf](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/marf/32/1799_2.png) [@Marf](https://forum.pinegrow.com/u/Marf)\
**Post date:** [March 6, 2020, 9:09am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/4 "2020-03-06T09:09:53Z")

</div>

@matjaz @RobM Thanks for the Developer Docs!

* * *

> [@Thomas](#):
>
> Yipiehh - I am a pioneer - and still a lil bit proud of it!

> [@Thomas](#):
>
> I was able to recreate my own “classifier”, still stunned that it works - and it does.

@Thomas It’s always great to suprise yourself and achieve something you didn’t know you were capable of. Well done, and indeed be proud!

Now with the Developer Docs available, you are maybe now able to optimize/improve your plugin or extend it and make it more advanced (don’t know if that’s needed or a wish). Or maybe, when you got another idea, you can challenge and surprise yourself again. And build another plugin.

* * *

@RobM Congratulations that you now are part of the Pinegrow team!

I’m a little bit confused, I thought you name was Robert (Rob), and now I see you are called **Bob** (by Matjaz). Is that an unfortunate typo, or do you have multiple names, or is in some countries Bob related to Robert. A big mystery… 🤔

---

<div class="post-metadata">

**Author:** ![Thomas](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/thomas/32/61_2.png) [@Thomas](https://forum.pinegrow.com/u/Thomas)\
**Post date:** [March 6, 2020, 10:39am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/5 "2020-03-06T10:39:43Z")

</div>

Hi @Marf

> [@Marf](#):
>
> I’m a little bit confused, I thought you name was Robert (Rob), and now I see you are called **Bob** (by Matjaz). Is that an unfortunate typo, or do you have multiple names, or is in some countries Bob related to Robert. A big mystery… 🤔

Bob is in fact the shortening of Robert (as far as my pidgin-english isn’t leaving me). And another short form is Rob. So in real life, he prefers being called Bob - in digital life Rob. And his mother - for sure - will say “Robert, did you already … ?” 🙂

> [@Marf](#):
>
> Now with the Developer Docs available, you are maybe now able to optimize/improve your plugin or extend it and make it more advanced (don’t know if that’s needed or a wish). Or maybe, when you got another idea, you can challenge and surprise yourself again. And build another plugin.

That’s the plan. And honestly, this exactly would make PG so interesting even for others.

Recently, I stumbled upon an article about [Monica.css](https://meowni.ca/posts/monica-dot-css/) which is more or less based on the inspiration I had for Reginald (almost 4 years ago). The “too much” and the “every framework has cool things - let’s mix em together” are just the two most important ones. The Sass work was first - and the Plugin work fit into this, nearby perfectly.

Applications like Pinegrow could rule - if only enough people out there would know about it!

Cheers

Thomas

---

<div class="post-metadata">

**Author:** ![RobM](https://avatars.discourse-cdn.com/v4/letter/r/278dde/32.png) [@RobM](https://forum.pinegrow.com/u/RobM)\
**Post date:** [March 6, 2020, 10:56am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/6 "2020-03-06T10:56:46Z")

</div>

Hi @Marf

> [@Thomas](#):
>
> Bob is in fact the shortening of Robert (as far as my pidgin-english isn’t leaving me). And another short form is Rob. So in real life, he prefers being called Bob - in digital life Rob. And his mother - for sure - will say “Robert, did you already … ?” 🙂

🤣 😂 😅 🤣 😂  
Thanks for the explanation, @Thomas Yup, this. In my family, my dad was Robert, my Uncle was Rob, his son was Robby, and I was Bobby. We didn’t talk to the rest! 🤣  
I’m agnostic about being called Rob or Bob. Around town some people call me Bo - he is our mini-donkey and I have a shirt with a picture of him, his name, and our farm logo. Some people thought it was my name and I’ve hated to correct them. The only time I’m firm with my name is in my publications - gotta keep up a professional reputation!

---

<div class="post-metadata">

**Author:** ![schpengle](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/schpengle/32/238_2.png) [@schpengle](https://forum.pinegrow.com/u/schpengle)\
**Post date:** [March 7, 2020, 4:43pm UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/7 "2020-03-07T16:43:27Z")

</div>

Well done mate! And congrats on joining PG team, FINALLY, GIVE MY REGARDS TO YOUR MUM  
**Robina**  
? 🙂 hee hee hee

---

<div class="post-metadata">

**Author:** ![RobM](https://avatars.discourse-cdn.com/v4/letter/r/278dde/32.png) [@RobM](https://forum.pinegrow.com/u/RobM)\
**Post date:** [March 8, 2020, 3:51pm UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/8 "2020-03-08T15:51:43Z")

</div>

Where is the groan emoji?!?!?!

---

<div class="post-metadata">

**Author:** ![Robert](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/robert/32/2509_2.png) [@Robert](https://forum.pinegrow.com/u/Robert)\
**Post date:** [March 26, 2020, 7:47am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/9 "2020-03-26T07:47:23Z")

</div>

I was trying out Pinegrow. I use Metafizzy’s Flickity, Packery, Isotope and infinite Scroll JavaScripts.  
[https://metafizzy.co/](https://metafizzy.co/)  
Pinegrow Support pointed me to the forums with a question I had.  
Would it be possible to add support and visual controls (to modify script options + reload) for JavaScripts through the plugin system?  
Or are plugins not for changing snippets of JavaScripts ?

---

<div class="post-metadata">

**Author:** ![RobM](https://avatars.discourse-cdn.com/v4/letter/r/278dde/32.png) [@RobM](https://forum.pinegrow.com/u/RobM)\
**Post date:** [March 26, 2020, 9:13am UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/10 "2020-03-26T09:13:20Z")

</div>

Unfortunately, at this time Pinegrow really only supports HTML snippets and alteration of HTML files on the front end. Pinegrow is agnostic about what is added through the snippets, so you could make a library of scripts to add to the front end, I think. I haven’t tried it, yet. So, unless you can do everything you need through attributes (I saw some aspects of Flickity can be used this way) or you want inline scripts, a Pinegrow plugin isn’t the way to go.

---

<div class="post-metadata">

**Author:** ![Robert](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.pinegrow.com/robert/32/2509_2.png) [@Robert](https://forum.pinegrow.com/u/Robert)\
**Post date:** [March 26, 2020, 1:45pm UTC](https://forum.pinegrow.com/t/introducing-support-and-new-resources-for-pinegrow-plugin-developers/3841/11 "2020-03-26T13:45:37Z")

</div>

Thanks for explaining. I’ll keep editing the JavaScript options snippets by hand in VSCode. My trial has expired and I haven’t yet checked out everything I wanted to. See if I can tickle another week or so out of Pinegrow.  
EDIT: Just emailed Support. Let’s see if I get another 7 days.
