2p In terms of saving time. I would go for wordpress. it is not some people's idea of elegant under the hood, I used to be cynical, but in practice it is the most versatile CMS, and has a wide selection of plugins, and is easy to develop.. Chances are you have everything you want.
Joolma is just terrible, and drupal has its fair share of problems. ________________________________ From: Michael MacFadden <[email protected]> To: [email protected] Sent: Fri, 2 September, 2011 15:20:25 Subject: Wave Web Site All, There has been several threads on the usefulness of the current wave web site, the lack of consolidated information, and the feasibility of maintaining the current site. I would like to get some ideas on the infrastructure we should use to maintain the site. I strongly believe that we will have more luck maintaing the site if we use some technology that is easy to use, well understood, and that can create a rich site that is "easy" to maintain. I think whatever technology we choose should meet the following requirements: It MUST support an arbitrary layout. We should be able to design whatever layout we feel is effective. It MUST support a reasonable set of HTML constructs, things like images, tables, rich content (video), etc. It MUST be able to support revisions (i.e. versioning). It MUST have some sort of visual editor. It MUST support CSS for styling. It SHOULD have some ability to tie user accounts and permissions to your Apache account. It SHOULD a common technology with a wide user base and good documentation. Basically, I feel like for a project that represents a web-based technology, it is important for us to have a good looking, easily updatable, and usable web site. After all if we can't present a well designed and good looking web site, then how can users have confidence that we can build an advanced web based collaboration platform. There are many things out there like Joomla, Drupal, Wordpress, etc that would probably fit the bill. So I have a few questions. What do we want to use? What are we "allowed" to use within the apache infrastructure? If we want to use something like a open source CMS, how do we go about doing that? If we get any kind of consensus, I volunteer to get that infrastructure in place. Thanks ahead of time for your feedback. ~Michael
