Deprecated - Drupal core

The current aggregator user interface does not work especially well for novice users. Words like attribute, tag, and bundle should not be used. I propose replacing this system with a more direct categorization system.

I am currently running a number of drupal sites (virtual domains using a common code base, and individual databases). I now want to create an administration site, whereby I can create nodes that will be seen by all of my drupal sites.

The way I thought about doing this is to use drupal's database prefixing functionality, and creating a new module 'sharednode', and an associated shared 'sharednode' database, that can be accessed by all of my sites.

I have tested several menu-modules, but they don't really work like I want them to.

I wrote my own block that checks ?q=... and shows a menu when it matches with a table I created in the database.

works fine, but now I want to know how I can see if a node is under a "vocabulary" in the taxonomy

e.g.
Introduction (node n° 10)
--Lalalala (node n° 14)
--Tralalala (node n° 16)
Where in the database can I find that node n° 16 is a therm of the voc Introduction?

a query would be fine, not one of the thousands functions in drupal :(

hey. is there any way to put in a bit of text to "introduce" you to a particular module page? (like before the events list for the events module)

something like the drupal description appears on the indx.php page of this site...

i suppose i could hack it in my creating another block area above the main display area (i think i remember some discussion of this on one of the lists a while back) and then putting specific paths limiting them to specific pages. seems sort of hackish though.

What about a content conversion architecture that looks like this:

--> INPUT converter --> Internal Rep      --> OUTPUT converter

    Wiki-in                                   
    OOo-in        -->   XML(for example)  --> XML out (incl. XHTML)
    XML-in                                    PDF out
    MsOffice-in

The converters could have an internal architecture that allowed them to be combined, piped, etc. If categorizing is part of the Internal Rep, then input streams could be piped, after basic format conversion, into a Categorizer component that could either categorize automatically, or require user input. Themes/templates could be part of the (XHTML) OUTPUT converter.

Thoughts? Disclaimer: I am a Drupal newbie

I have been examining the Drupal source to learn it properly. I have been looking at xtemplate.xtmpl, css, theme.inc, and some modules to see how it all fits together.

After doing so for while I think it will be easier to tackle Drupal right from the source.

Which routine parses the URL sent from the browser before sending it to the right module?