We are often asked by developers what we are looking for when we screen submissions for the Add-on Library? Is there a particular coding style that must be followed? What types of things need to be avoided? How do I know if my add-on is secure? Well, after a long process, we are happy to release our guidelines for add-on developers.
It wasn’t planned as such, but the summary checklist has exactly 56 items on it, and to me, this is a perfect number.