Best practices guide for extension developers

It has been said more than once that the documentation for extension developers is scattered in various locations. Further, while these documents (when they exist) provide useful information for how to do something, it is often possible to accomplish the same end by various means, and these guides offer little to help developers select the best tool for the job.

The arguments for prioritizing this initiative are that:

• it will result in better code, which means:
  • better user experiences
  • better developer experiences for folks who have to work on someone else's extension code
• it will improve the developer experience generally, which will make it easier to attract/retain developers to our community.