Now that we invited developers to participate in developing Pinegrow extension, it’s a good idea to coordinate a bit in order to avoid multiple people/teams working on the same thing.
There is no problem in having many people trying to crack the same nut, each with their own approach and confidence that their solution will be the best - as long as this is an informed decision based on the awareness of what others, and especially the Pinegrow team, is doing.
We want to avoid situations where a developer would be creating extension for X and at the same time we would also be building the same feature, whereby decreasing the marketing potential of the developer’s extension.
So, for the sake of transparency, these are the extensions that Pinegrow team is currently building or planning to build in the near future:
- Tailwind is gaining in popularity, so we are building a prototype integration to see well it could work with Pinegrow.
- Support for responsive images will be implemented as a core Pinegrow feature.
- Improved Blocks / Components where it will be possible to have per-component style / JS and only include that in the project if the component is actually used. This feature will also make it easier for other developers to create libraries with reusable blocks / components.
This is not the exhaustive list of what we’re doing, rather it’s a list of features that we are building that are good candidates for implementing as Pinegrow extensions.
And if you’re in doubt how the extension that you’re planning to build fits into the Pinegrow roadmap, just ask us about it.