A "CSS Consolidator" or Tree-based CSS Editor

I was trying some new layout on a couple of my web pages the other day.

Whenever I do that I always end up with a bunch of different CSS files all over the place, and it becomes increasingly different over time to keep them clean.

Being a programmer, I'd like to follow the DRY directive: don't repeat yourself. In order to do so, my CSS files would ideally be organised in a hierarchy: some CSS directives apply to all my pages, so they should end up in global.css, while others apply only to the astronomy section of my pages and should therefore be in astro.css.

Also, I like to seperate CSS files according to function (layout.css vs. typo.css).

In the end, I always have enough of those files to lose overview.

What I would need is a tool that displays all of my CSS directives along with where they come from. That way, I could move them easily from one file to another, or up/down the hierarchy if needed.

The tool must have an automatic consolidation feature that would move directives up the tree as far as possible.

I would not want to be able to graphically browse through my (X)HTML and apply CSS rules using the mouse. I would really want this tool to be able to work on existing or create a hierarchy of CSS files.

Does that make sense?

A Joomla to Drupal converter

I will absolutely never write a converter that takes content from a Joomla-driven site and tries to recreate the same site in Drupal.

First of all, the concepts of the two are far enough apart to make that very difficult to do automatically. A user would have to define quite a lot of things in the process, such as matches from categories to taxonomy, possibly for each node individually. That GUI would not be very easy to understand.

Also, there is no way I could ever build a tool that converts Joomla themes to Drupal themes. The process would therefore be semi-automatic, at best.

Joomla has modules and components, which extend the functionality. Drupal also has modules, but of course they are different. A converter would only make sense if it could handle at least the most common Joomla modules and components. A shop based on Virtuemart, for example, would have to be converted to a similar Drupal module. That's a bit like "yet another converter".

A Joomla to Drupal converter would be a good thing to have, and I could surely use one right now, but I think re-creating the site manually will be faster and lead to better results.