The Design of a CMS aka What Drupal 7 should be

I've only used Drupal for 2 months, but I've found my way around, read through the entire API, the docs, and can (with some exaggeration) say that I can do most of the things that Drupal has to offer. I'm new to Drupal, but I've had much experience with other CMSes such as Wordpress, SilverStripe, and ModXCms before. Before I start, this isn't another one of those "I hate Drupal" posts. In fact, I love Drupal, I think that it is awesome. But it definitely has room for improvement, and I will attempt to cover my specific points here. Basically, I'll try to cover the way I think Drupal should be.

Important Fundamentals

These are my key points, the changes I feel that are the most important.

• Backend. Starting off with the fundamentals, I'll cover the Drupal backend, the stuff you see when administering the installation. I'm not sure if this was a major core decision from the start, but in Drupal, unlike most CMSes, there is a thin line between the backend and the frontend. Of course, some people hate this, but I'd have to say I'm neutral on this. Of course, what I really like in other CMSes is that there is an actual administration interface. It's kind of hard to explain, but I guess a central admin dashboard which allows you to accomplish a few fundamental actions (but not nearly as comprehensive as the Administer screen) straight from there. Look at the Wordpress dashboard. (This has been discussed at http://groups.drupal.org/node/9570). AFAIK, Drupal has had the same backend sine 1.0.
  My suggested action: a redesign of the administration backend, possibly adding a central dashboard (to make it look (slightly) more like Wordpress).
• Backwards Compatibility. That's right. Here we go again. It's been said before, and I'll say it now. As most of the people involved with open source software well know, there are a few open source best practices. Work with the community when designing. Have a mailing list/discussion area for questions and answers. Have a dedicated issue tracking system. Drupal follows all of these except one. Backwards compatibility. I understand that at Drupal's creation, Dries decided that Drupal would sacrifice backwards compatibility in exchange for better, cutting-edge code, among other things. It's not worth it. It just isn't. I'd much rather have slightly less features, than not have the opportunity to upgrade without worrying whether my data is safe, without having to download new versions of all my modules and themes. I want a clear upgrade path. I want the opportunity to do a WordPress like update. Download archive, upload files, go to upgrade.php, you're done. Now Wordpress even has a built in upgrade option. (You might notice I'm referring to WordPress a lot, but that's simply pointing out the good points of WordPress that apply here. I am not affiliated in any way with WordPress, just an avid user.) Discussed: http://drupal.org/node/229163#comment-754958. I think AusValue makes some very good points there. I have to install an old version of Drupal because the issues module is not updated to Drupal 6. That is not the way it's supposed to be. Backwards incompatibility is making it harder for me to use Drupal. Each day I wonder: what will happen when Drupal 5 becomes unsupported? Will I have to risk everything, lose some of my site's functionality and switch to the next version?
  My suggested action: Add backwards compatibility. Please. At least add some. I might be too late in the game, but I think that there should be a rewrite of Drupal. WordPress got rewritten at 2.5, with huge improvements, then again at 2.7, which turned it into something amazing. (By the way, they redid the backend each time).
• Simplicity. Drupal is very powerful. I've understood that since the first time I saw it. And that's the problem. One of the only things I don't like about Drupal is the complexity of the system. I guess this ties in to the Backend part, but whenever I use Drupal, even to create a simple page on my website, I am overwhelmed with options. Page or Story? Full HTML or Filtered HTML? In the menu or not? Alias X or Alias Y? Coffee or tea? Paper or Plastic? You get the idea. I guess I only use half of those options. I mean they should be available, but they shouldn't take up most of the screen, they shouldn't jump into my eyes. Again, look at WordPress. It makes use of a separate backend theme, and spreads out the options into the sidebar, and makes them unobtrusive and easy on the eyes. I can create a page without worrying or even having to notice those options.
  I'll give you another example. The navigation is a mess. I put it in the sidebar, and the ugly mash of links becomes extremely visible. Why do the users need to see a Create Content button? If they want to post a forum topic, they'll go to the forum, and do it there. If they want to create a project issue, they'll go to the project page and do it there. Why add additional burden on the user by providing them with a link that does not make much sense? I'm forced to limiting the navigation only to administrators (namely me), and showing the users a custom hand-coded navigation box that is not as obtrusive to the eyes.
  Simplicity is key. It lures huge amounts of users, it makes it easier for existing users to work in the system. It makes creating web sites fun. But now, I dread each time I need to update my site. I'm spending much more time working on my site than I should be. Drupal should be made easier to use. I guess at least reorganizing the navigation would be a start. I find that the more complex a CMS, the harder it is to use, but I know that that does not have to apply.
  My suggested action: Make Drupal easier to use. (I've covered specifics above.)

Convenient Additions

These are the features that have a place in Drupal, but I feel are not as important as the ones above.

• Module Control and One-Click Upgrading. WordPress has a very convenient core feature (has had it from the start), where on the Module page, you can activate and deactivate modules. It also notifies you if there is an updated version of a module available (same with core). And it also allows you to one-click install modules straight from your WP install. All these features would greatly benefit Drupal.
• Complete Wiki Module. There should be a (single) module that provides all the features of a wiki and allows you to create a separate wiki section on your site. You can currently do that be installing 5+ modules, and doing 30+ minutes of configuration, but it should be combined into a separate wiki module, with a separate content type, like the forum module.

That's all I can think of right now, but if I think of something else, I'll add it to the post. But now, I want to hear your opinion. Where do you agree with me, where was I wrong? Maybe I don't understand something somewhere, so please tell me, and I'll make the necessary corrections. Hopefully, we can turn this into a central document for wanted future features.

Daniil K, the 13 year old