Web site
GRASS Web Site planning
The current GRASS web site appear a bit overloaded and unmodern (since it has been kindly handcrafted with vim since 1998, of course following some evolution from plain HTML to HTML/PHP with RSS integrated). The question is:
- go Content Management System (CMS)?
- or stick with static pages?
To keep in mind:
- traditionally low number of contributors (hey, this could be better with a CMS)
- mirror sites want to copy/clone the site without more efforts than using rsync (i.e., static copy)
- the new layout should be modern, fresh and attractive
Nice sites
Here a list of sites which are looking nice:
- Geotools.org
- System: Sphinx
- Advantages:
- Page files can be maintained in SVN
- Disadvantages:
- No WYSIWYG editor
- CMS Made Simple
- System: CMS Made Simple
- Advantages:
- WYSIWYG editor
- Access control via roles
- Static mirroring seems to be possible via http
- Very light system, installed in a few minutes
- Disadvantages:
- Requires browser for editing
- OSGeo Foundation
- System: Drupal
- Advantages:
- WYSIWYG editor
- Access control via roles
- Static mirroring seems to be possible via http (? check)
- Can be run within OSGeo's Drupal server
- Disadvantages:
- Requires browser for editing
- Rather heavy system, installation may be complex but OSGeo can provide it
- Geopublishing
- System: Drupal (? unsure)
- Advantages:
- see OSGeo above
- Disadvantages:
- see OSGeo above