Personally, and this opinion is mine alone (ie: this is not a statement from Pinegrow Pte. Ltd), I think that the problem is not a lack of documentation, we offer hundreds of them, written or video, and overall, regardless of their “age” (we have very recent documents as well as some older ones), as long as we have guaranteed the backward compatibility of the WordPress builder, they are all valid for the general understanding.
In my opinion (I repeat, this opinion is my own) the problem is that - by obvious choice because this very exhaustive documentation exists elsewhere - we do not document the functionality of the WordPress CMS. Thus, since beyond the use of Pinegrow, it is necessary to know the WordPress CMS to understand the subtleties of a successful integration, this is an unexpected pitfall for many users who were expecting a much simpler learning curve.
Pinegrow does not reinvent WordPress, it offers a visual and simplified integration of features that would otherwise be difficult to integrate but the development logic remains classic and follows the development guidelines specific to this CMS.
Unlike a page builder where the user is put on rails and where understanding what is going on in the background is not necessary, with Pinegrow, the integration choices are yours and depend on your understanding of the CMS. Nothing will stop you from making mistakes because you think you understand the purpose of an action when it turns out to be incompatible with the situation. Nothing will prevent you from forgetting to define key elements (loops, site content action etc …)
So, of course we have documented the essential prerequisites, and we will continue to provide documentation on Pinegrow’s features and how best to create effective themes, but to create complex themes, hundreds of other subtleties exist in the WordPress documentation and can be implemented through the use of combined smart actions OR PHP snippets.
As you are aware, I’m an experienced Pinegrow user, a former hand developer of WordPress themes (so I have a very good knowledge of the CMS) and yet, I regularly consult our documentation and even more regularly, the WordPress documentation for all my theme developments and experiments.
Because Pinegrow makes it EXTREMELY easy to test hypotheses, I do trial and error on a daily basis. It takes a few seconds and sometimes, by chance, it even allows me to discover new solutions.
Thank you for reading me.