Okay, maybe I should clarify what I am doing and why I am doing it.
First of all, one of the major reasons Massassi isn't featured in the top of major search engine results is our use of FRAMES. Frames are what allows the right side of the massassi main page to scroll independently from the menu. When search engines crawl our pages, they don't get any navigation elements (because they don't see the menu).
Second, the Massassi admin script is insecure. Enough said.
Third, the Massassi admin script is not centralized. Things like the admin for sotd and mats are not in the same place as news and levels. This needs to be fixed.
Fourth, the Massassi admin scripts are all in various states of disrepair. They were all written when I was a lot younger and a lot less experienced. I'm not rewriting everything, more like refactoring.
Fifth, a lot of them can be grouped together. For instance, I'm going to make a generic "files" admin script. It can be used for all the stuff in our programs, levels, mats, 3dos, etc. You can add any categories and add any file type under them. Comments will then be available for every file type.
Sixth, I want to implement a lot of the suggestions people have made. In order to do this, I need a solid foundation for the site. This foundation needs to be on a set of secure, quick, and easily expandable scripts. I have accomplished that. I have implemented a new news script in about 2 hours. That shows how easy it is for programmers to work in the new foundation (as long as their familiar with templating, OOP, and some of the freely available PEAR classes).
Seventh, I'm making a "page" administration script. All pages will be thus saved in the database and outputted based on current templates. This means all "static" pages (tutorials, info pages, submission instructions, etc.) will all be stored in the database and outputted as files whenever the templates change. We will get the benefits of a dynamic solution without the overhead. And it's *easy* to program (really, I'm about halfway done already and I've only worked on it for about an hour or two).
Eighth - and this is probably most apparent to end-users. We will have the ability to completely change the site design simply by swapping out templates. We can then output all the files we need to and the entire site is updated. So even if you don't like the design shown above, at least THIS time, it won't be a major undertaking to change it. To do the conversion right now, we're basically converting thousands of pages programmatically, and at least hundreds manually. In the future, once *all* content is in a database, we will easily be able to make sweeping design changes with a few clicks.
Hope this clears up some confusion.