Changing the Tool?

Sarah weighs in with some good arguments for Manila, and David adds that the bottom line is making it easier. So let me ask this: If both of the front-running tools have their issues, then should I be choosing one based on my assessment of what the future may hold for it? From all accounts, MT seems to be getting more attention than Manila in development terms. But there is Kern, who is basically doing what I propose and who happens to have two of the major Manila players around working for them. And, that whole Harvard initiative that Dave is undertaking gives me a great deal of hope. He’s using Manila. He’s trying to implement schoolwide. I can’t imagine that the Crimson-ites won’t express the same concerns that we have(even though they are so much smahtah…) I would think that would bode well for development of the tool. On the other hand, the issues we have deal most with ease of use and intuitiveness, the basic building blocks of the whole system. Doubtful that that will become easier.

This is a MAJOR decision for me now. I’ve gotten the superintendent’s go ahead; I’m presenting to a board committee in early May. The planning time for this is enormous. Our current site runs on a UNIX box, but we’re going to build the new site on NT. We have 3000 pages on our Web site, and I’m basically saying we start all over. We want to build an Intranet along with it. Gulp. Anyone have a quarter?

Right now, I need to get some questions answered. Things like will MT Pro allow people to create their own sites? Like how do you get an RSS feed into a Manila page? Like, again, what can and cannot be templatized in Manila and MT? (I swear, the thought of having to go in and configure a dozen settings in Manila for each Web log makes me crazy.) More to come, I’m sure.