I tried to get the Games Industry software developers to even discuss forming a union for 15 years while being a senior developer for EA, Sony and several smaller houses... I finally gave up. Developers are dumb asses, is my only conclusion.

Actually, there is a comprehensive networking and collaborative side to this WebApp, and those clients selecting to use the app with no network simply loose out on that feature. However, it's fully available within Intranets. Plus, mobile workstations can operate without any connection and then collaborate filly and securely when a connection is established. I'm somewhat amused by how much people have read into my situation from the scant info I've offered. Simple story: limited resources, and a client that wants it everywhere, with it scaling to consume available resources if present.

Limited resources all around: not enough time, not enough engineers, and not enough money.

Perhaps it was the lack of documentation or bread crumbs to follow that led me to think it was dead. (It's somewhat of a pain that searches reveal very old documents that ought to simply be removed.)

After searching around for two days, it did not look like the project was active any longer. Simple as that.

Actually, technically, Drupal IS a framework that happens to come with a CMS built in that framework. The Drupal API is huge, fairly well organized, modular and capable of creating practically anything. Comparisons with Drupal are difficult because it is not JUST a framework but is ALSO a content management system. I've heard the term content management framework used in an effort for clarity.

A major goal of yours should be sparking interest and a desire to learn more from each class the students attend. A good way to do this is to have each class give the students something they can walk away with and use immediately in a manner they appreciate.

For example: class one could cover the basis of what a web page is, and how the html, css and so on make the page. Don't go into detail, just hit the high lights of each, compartmentalizing the web page elements and their respective purpose. Don't say how they are constructed, only describe what they are used for - html=content, css=layout, php=logic and so on. Then give them one example of editing a MySpace page, showing something simple for students seeing this for the first time, and something advanced for the students that already use MySpace Editors for their own pages.

Class one, you give them a mental picture of a web page and then show them how to modify a MySpace page. That should get many students' attention. In the following classes, touch upon each area a bit, exploring your student's interest and letting the class explore. They may go into Flash games or widget development, it's hard to say. But in each case, it's not to hard to take baby steps into a complex area. Remember, you're not making CS graduates here, you're giving a class of students a "guided interactive tour" with the goal of sparking their interest and creativity to learn more.