GATE Village Technical Overview

While I could, I suppose, list the complete technical overview of GATE Village, I'm pretty sure that would be something almost nobody would read and few of those that did would find it very interesting. That being said, I think there are many people -PARTICULARLY the experts I wish to attract- that are interested in the basic architecture and design decisions if for no other reason than to convince themselves of the veracity of GATE Village. So, I'll attempt this discussion and entertain questions (via replies) to expand where there is interest.

I see the Village deployment in four somewhat distinct (but certainly related) ways:

1. The functionality that needs to exist to allow the novice to utilize the Village effectively (where effective means the ability to promote themselves and/or their business in the way and to the people they desire).
2. The functionality that needs to exist to allow trusted experts at web design and web application building to utilize the Village effectively (where effective means the ability to produce the web pages, web applications, and web communities in the way that they and their customers desire).
3. The functionality that both 1 and 2 require and expect as given, like automation, Search Engine Optimization technology, email integration, and mobile access.
   
4. The infrastructure that needs to exist to ensure that 1 and 2 are possible, that the Village is robust, resilient, performs well, and is scalable.
   

I will follow this topic up with four more (mostly just to make them all a reasonable size).