#3 Simpler directory structure

[Henrik Vĺglin]

Sure Mambo is a complex piece of software, but does the
directory structure really have to be that too?

As a transition method and recommended also for the
future, you might consider adopting RDF and OWL full
out for the MozXML. Doing this you don't even have to
actually edit the physical directory structure until
the transistion is fully done, but just set up an
separate onthology and then there probably be no
problems with old remaining hardcoded references.
(Using RDF/OWL could also go well together with my
previous feature request suggestion "Cross- & simple
navigational URL:s"
http://sourceforge.net/tracker/index.php?func=detail&aid=1071313&group_id=119308&atid=683591\)

There are several RDF and OWL php Open Source
projects/products that you might use to integrate for
that very purpose, unless you consider the already
integrated MiniXML is adequate for that.

Anyways, I suggest a directory/ontology structure for
MosXML where the layout from the software top directory
look more like this:

classes/ - remains mostly as it is with a few additions
flash/ - content of the
'/flash/flashClasses' directory is moved here

components/ - remains but is restructured
core/ - all components that are
non-optional
administrator/ - is moved
here from the top directory
editor/ - is moved here
from the top directory
language/ - is moved here
from the top directory
extensions/ - move all the contents
of the current 'components/' directory here, unless
there's more that are core parts and non-optional
(which should then go into the parallell 'core/' directory)
mambots/ - move all the contents of
the current '/mambots' directory here

content/ - this is where the actual site content should
go, ie the XML, images etc (in case of multisite
subsites, they all go as subdirs with the same layout
as the one described for this one)
images/ - for images as content specific
to the web site
stylesheets/ - all CSS stylesheets
specific to the web site
media/ - all media content specific to the
web site

libs/ - these are resource libraries used in the site
downloads/ - is moved here from the top directory
modules/ - is moved here from the top directory
images/ - is moved here from the top directory
includes/ - is moved here from the top directory
javascripts/ - is moved here from the current
'includes' directory
flash/ - is moved here from the top directory,
excluding the '/flash/flashClasses' directory
stylesheets/ - all core stylesheets is moved here
css/
xsl/ - move all the contents
of the current 'xslTempelates/' directory here
themes/ - extension theme files & subdirs
(stylesheets, images etc)

Then most of the single files in the top directory
should be stuffed into the appropirate subdir too, so
that the only files in the top directory be an
index.php, a README and possibly one or two more really
core files.

(I reserve myself for haven forgotten something or
misunderstood some concepts of the current layout as I
haven't used Mambo myself before)

Once again; if this is something you have in mind to
do, I might be
of service in helping out. My motivation - as stated in
one of my previous feature request - is that I would
want to use and integrate
such a web application for the c3ms project
(http://sourceforge.net/projects/c3ms/) which I'm heading.

[Henrik Vĺglin]

Logged In: YES
user_id=62104

umh, the formatting of the directory/onthology structure
didn't stay when submitted. So here I attach a text-file
with formatting the way it should be in hope to get it a
little more straight across this way.

[Henrik Vĺglin]

a textfile with the formatted structure as it was supposed to be looking