I really like how Silverstripe core is kept so lean and mean whilst allowing developers to implement what is required. As a procedural ludite I have only just started to venture into developing object code and even I have now been able to implement a number of my own modules. In order to troubleshoot when things do not work, I think it is essential to know the order in which things happen. However I think my understanding of what happens is quite limited. I would like to find an explanation which refers to the different types of files used by Silverstripe when a module runs, and how these files and what they contain are brought into play and used. This would obviously make troubleshooting so much easier. On reading the documentation I have not been able to build up a clear picture.
Does anyone know where I could look to find an explanation which tries to give a reasonably detailed and clear picture of how it all essentially fits together?