Point one that emerged from this discussion - to update instances where we just diverge the responsibility to the Devs (“ask them to be compatible”) has been done in the instance of FAQ here
Screenshot below is what was prior, doc features updated content.
Again, if someone knows of more content where we do not motivate users to actually really move towards CP please list it here so we can act upon.
Also of course if above FAQ contains error or such please let me know.
As of point 2, where we should motivate and make it as easy as possible for people to develop for CP, I also put online https://www.generateplugins.com, a service to quickly spin up a (CP Compatible) Plugin.
I am wondering if we also should create a “code snippets repo” where users can share code snippets, perhaps a kind of “vetted” library. I was thinking of something like this example (that os from Toolset, it is a semi-public site, just as example) where snips are available for consultation. We could also use Gist of course, and link if somewhere useful. I think this could be helpful to address some tiny features that usually need a plugin but could just be a tiny Must use plugin file, for example.
This could speed up development process as the avid devs do not need to deploy a full theme each time or plugin, but could just gist their tiny bit of code that addresses one issue. Of course we’d need some sort of vetting process, just like we do have for Plugin directory.
And gist might be suboptimal for this as it is not a closed system (anyone can gist)
Thus a section in “developer guides” on our doc might be better.