Help with an Orchard CMS Request Lifecycle Diagram

Topics: Core, Customizing Orchard, General
May 31, 2014 at 2:16 AM
Edited May 31, 2014 at 2:40 AM
I am creating a diagram of the Orchard request life-cycle that looks like the following with fewer details:

My motivation is to understand how Orchard works, to customize Orchard in "the Orchard way," to build awesome CMS websites that solve real problems, and to help others learn how to do the same by contributing the diagram to the community.

One of my immediate goals is to nail down the steps before putting together the diagram. I have read the following two links:
I would like to include aspects of the life-cycle from ASP.NET MVC (e.g. Filters and Controller) and Orchard (e.g. Handlers and Drivers). It will include when each happens, what each does, code blocks in which we can put breakpoints, and how we can use each step to extend Orchard. Once that is down, I would like to include other parts of the cycle such as NHibernate and Castle.

My current notes are here:

What I am wanting is feedback, support, or encouragement. Will this be useful to the community or just to me? Am I on the right track? Is there anything important that I am missing early in my attempts? Does this diagram already exist (i.e. am I recreating the wheel?) If I were to put this in a GitHub repository or elsewhere, who else would be interested in contributing?

Thank you for any help.
Jun 2, 2014 at 7:38 AM
Bertrand's page definitely need an update. If I am not wrong, there was sth like this presented in last year's Harvest. But not sure. Anyway, I think it will be a useful document.
Jun 2, 2014 at 2:18 PM
Good feedback. I'll continue with it this week.
Jun 4, 2014 at 2:59 PM
Edited Jun 8, 2014 at 2:13 PM