simplifying the wyona directory structure

here are some thoughts on the wyona directory structure,
work in progress.

we currently do have libraries under /libs and under
/src/webapp/WEB-INF where shall they go?

same for docs. they are under /webapp/wyona/cms/docs and
/webapp/wyona/cms/pubs/wyona-cms-docs/

the wyona menu is in the eth pub when it should go somewhere
centrally, we need to make a system-wide css and image matcher
(started in the root sitemap)

the way how subsitemaps override features of the root sitemap
has to be rethought, and made consistent. we are not sure if
cocoon has all the power we want to factor out common functionality
(menu, bitfluxeditor, scheduling, publishing, revision control etc)
into the root sitemap, and make the publication sitemaps much simpler
(and more consistent)

the directory structure inside a publication needs to be refined.
we currently do not have a consistent place to put .xsp, neither
do we have a /bin for publication-specific shell scripts

the goal is to make publications self-contained so that we can
manage cvs better, and give our clients cvs access to their publication,
but not the whole source tree. this requires a way to store the
publication-specific classes inside the publication (/java maybe?) yet
still be able to deal with the CLASSPATH in a sane way.

there are probably many hidden dependencies between various publications
(they grew organically ..) so it would make sense to test them by
removing other publications. 

in that vein, some of the older publications probably do not support all
our new core features, and should either be updated to reflect the new
functionality, or be dropped.

hm, after some discussions these items better go to the bugtracker i
guess :)

-gregor

--
Gregor J. Rothfuss   [email protected]  +41 1 272 9161
Software Architect   Wyona AG, Hardstrasse 219, CH-8005 Zurich
Open Source CMS      http://www.wyona.org http://www.wyona.com