Here's a wish..
to parameterize or somehow externalize all html/css coding and other factors of packages that can (and likely) vary by installation, such as OS, style etc. (Partially ongoing with TIP Nbr.8)
Examples:
1. Calls to noncore applications, such as ispell could reference a parameter or some kind of package config file with the ispell filepath.
2. Embedded html, css and templates could be referenced via parameters as default values. This way, the defaults can be included in CVS, and changed without negative consequences from varying from the defaults.
Separating site content from OpenACS technology decreases the overhead in keeping a site current (not to mention making it easier to manage installation variations).
The idea here is to increase the number of CVS development, beta, and release subscribers (and thus their participation in the process). When the number of CVS subscribers increase, the loop between bugs, bug fixes and site updates (as well as external feedback and suggestions) gains momentum. The participating community grows and everyone benefits.
