I have been working on some modifications I want in DNN but with so much information it's hard to get started, I looked at, bookmarked, and downloaded a good deal of the documentation and have read about 25% of it, which is a lot - I'm wondering if there's a more outlined, hierarchical, and brief summary of DNN as a whole.
What would help speed up the process for me in understanding the inner workings of DNN would be an outline of all the files and folders in the DNN file system and a similar hierarchically summarized outline of the database tables/schema with fields and a one sentence summary description of each of the individual items in these two outlines.
That would provide a great specific overview of the entire DNN architecture that would be a great basis from which to talk about DNN, like a common denominator for developers and build from there without a big learning curve for people just coming into it. A similar outline of the CSS, skin objects, and module hooks would also round out the architecture overview.
From a development stand point this simple and universal starting point for all developers no matter what their length of time with the DNN project would greatly unify the development process as an accepted "step one" that all mod'ers could base development from.
Besides the full documentation, a handy "cheat sheet" like this just makes referencing, thinking about the big picture, and innovating new functionality easier and quicker being more readily accessible when developing. I appreciate the amount of documentation in DNN but having a more digestible form of it is also needed and I haven't come across it as of yet though I've searched DNN and many 3rd party sites for it.
If anyone knows where I can find and download these kind of outlined hierarchies of DNN's file and folder structure as well as database tables and fields with a working chart of implementation processes showing the style and module hook points (such as where to change css styles and hook in a new function in a module) I'd appreciate it. If this idea hasn't been brought up to the DNN team before I think this would help developers with a very quick and visual way to develop functionality for DNN rather than reading lots of documentation and getting kind of lost in it.
Thanks