I have been busy with other project lately myself and have been hanging back like Dave, but this is something I thought I should really speak up on.
I know the idea is to make it "easy" for people to use the kit and get their sites up and running in no time. I installed a drupal test site a while back, and had some other non programmer/ non web people look at the admin interface. Their main issue was that the admin interface was far from "easy" to understand. dale said, "Will there be some sort of promotional sandbox? "Here...look how powerful and easy this kit is to use?" Something along those lines???" We can certainly sell everyone on the idea of the functionality of this "kit", but honestly I don't think we will be able to show how "easy" to use it is unless we redesign the admin interface somewhat because it is not exactly "easy" or intuitive for the average user to understand. Given this I think it will make it even less likely that people who already have sites running to want to switch over, and make people who aren't very technically savy, intimidated at the very least. I know something similar to this has been talked about before, and I realize that it is mostly the terminology that Drupal uses that can be misleading or hard to understand. Since redesigning the admin interface would take too long, perhaps rewriting the documentation to more of a step by step tutorial with diagrams/screen shots to make setup and use as easy as possible. Basically what I am saying is that we may need a "DeanSpace Drupal for Dummies" guide or something to make it as "easy" as possible. Is this being done or has it been assigned? If not what do you all think? As for seperate modules, I think it would be a good idea to offer the basics for communicating to the network of sites. The problem is knowing what to design for in terms of languages and having a database or not. We need to figure out what group of people will not want to switch and why. Then target that group with the seperate modules. If we create great insturctions for the "kits", as suggested above, then I think the only people who will not want to switch we be those who have already devleoped tools for themselves and have already made interactive/dynamic sites. So I believe that those most likely to not switch, i.e. need seperate, non drupal dependent modules are the more technically proficient people believe it or not. So if this is the group we are targeting then these seperate modules should probably be made with ASP and PHP and be made to work with several different databases. Just my 2 cents.... err.... or maybe 3 or 4 ;) Toro --- Dave Pentecost <[EMAIL PROTECTED]> wrote: > Hello all > > I've been onboard since early on, basically lurking > and following the > email exchanges. But I'm glad that Josh S. has > brought back the idea of > non-Drupal modules. I suggested a while back that > there be an MT module > for bloggers, to put into a sidebar. I think that if > we reach out to some > of the more political webloggers using MT we could > get help creating and > distributing it. > > While you folks are busy with Drupal, I'll start > looking into this angle. > If anybody has additional ideas on separate modules, > let me know. > > Dave Pentecost __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com