Web site

From GRASS-Wiki
(Redirected from CMS)
Jump to navigation Jump to search


Since 2020 managed at https://github.com/OSGeo/grass-website

2012 - 2020

NOTE: As of 10 Nov 2012 the new Website is online!

Old thoughts and discussions below...

Prototype GRASS site

based on CMS Made Simple (here at FEM, we are running 10+ portals for two years)

Pages to be transferred from old to new Web site

HTML Site Map (reduced to the CMS related content): http://grass.osgeo.org/sitemap.html <-- we'll keep all material in an "archive" part of the Web site

HTML Site Map (complete): http://grass.osgeo.org/sitemap_full.html

  • ...

Pages already transferred

  • Home
    • impressum.html
    • copyright.html
    • contact.php
    • devel/grasshist.html
      • devel/grassreleases.html
      • devel/vanwarren.html
      • gdp/grassclippings grass_movie_CERL_1987/ newsletter/
  • download/index.php
    • download/software.php
      • Linux
      • platforms/wingrass.html
      • Mac OSX
      • download/cdrom.php
    • download/data.php download/data6.php
    • download/addons.php
    • download/logograms.php
  • gdp/index.php
    • gdp/manuals.php
    • gdp/tutorials.php
    • gdp/books.php
    • applications/index.php
    • searchgrass.php
  • Donations
  • '
    • community/index.php
      • community/usergroups.php
    • community/commercial.php
    • bugtracking/index.php
    • community/sponsors.php
  • devel/index.php
    • devel/i18n.php
    • devel/svn.php
      • devel/svntags.php
      • devel/grasssvncommit.php
  • community/get_involved.php

Pages to be completely transferred from old website to new one

These pages are yet partially transferred:

    • devel/grasscredits.html
    • screenshots/index.php
  • community/support.php

Pages to move to wiki

  • grid3d/ (moved to Help_with_3D)
  • statsgrass/index.php (moved GeoStatistics))
  • statsgrass/grass_geostats.html
  • intro/modelintegration.html
  • nviz/index.html (moved text to NVIZ)
  • devel/roadmap.php Roadmap
  • community/team.php Team
  • faq/* FAQ

Pages to be archived

  • GRASS News Archive
  • GRASS GIS mirror sites
  • conferences (entire folder)
  • community/germanlist.html
  • community/get_involved_de.php
  • mirror sites
  • newsletter/postercontest.php
  • devel/grass1to4history.html
  • download/data5.php
  • download/software_old.php
  • faq/index.html
  • gdp/general.php
  • gdp/installation.html
  • gdp/manuals_old.php
  • gdp/erosion/agnps/
  • erosion/agnps/agnps.html
  • gdp/grass5tutor/index.html
  • gdp/handbuch/index.html
  • gdp/landscape/r_le_manual5.pdf
  • gdp/neteler/index.html
  • gdp/raster
  • gdp/raster/r_water_fea
  • gdp/sdts/
  • gdp/sites/
  • gdp/stereo-grass/index.html
  • gdp/terrain/r_le_22.html
  • gdp/tutorial/grass_info_deu.html
  • gdp/tutorial/grass_info.html
  • intro/capabilities.html
  • mailing_lists/grasshopper_1995
  • newsletter/postercontest.php
  • newsletter/grassnews1.html
  • newsletter/grassnews2.html
  • newsletter/grassnews3.html
  • newsletter/grass_osgeo_news4.html
  • platforms/index.php

Pages to be newly developed

Inspired by other sites, some new content must be developed:


(a complete list of old pages to be allocated into above categories during the transformation process - are we able to automagically generate it?)


  • Home/Download ({os_detector} tag)
  • Imprint (Web statistics)
  • Copyright ("here")

CMS Made Simple editing tricks

  • Select editor to use in "My Preferences"
  • Error "Smarty error: ... unknown tag - ...":
    • You need to protect curly braces '{...}' with '<literal>{...}</literal>'

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

Update 7/2010: grass.osgeo.org is now running on new hardware on Debian Lenny.

Nice sites

Here a list of sites which are looking nice:

reSt + Sphinx

  • Geotools.org
    • System: Sphinx
    • Advantages:
      • Page files can be maintained in SVN
    • Disadvantages:
      • No WYSIWYG editor
      • I think the GeoTools site is about as fancy as you can get with it (not very).

CMS Made Simple

  • 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
  • a command-line admin tool called Drush is available.
"Drush is a command line shell and scripting interface for Drupal, a veritable Swiss Army knife designed to make life easier for those of us who spend some of our working hours hacking away at the command prompt."
  • Geopublishing
    • System: Drupal (? unsure)
    • Advantages:
      • see OSGeo above
    • Disadvantages:
      • see OSGeo above


  • LyX
    • System: PmWiki
    • Advantages:
      • Looks professional, it's very hard to tell that their front page is actually a wiki
      • Does not make the homepage look like a personal blog (/node12345) or wiki site
      • Wiki editing means low barrier to entry
      • Lightweight (200kb) & snappy
      • html→pmwiki converter: libhtml-wikiconverter-pmwiki-perl
      • The LyX people took good notes on how to set it up (here) and are approachable.
      • A good philosophy (more)
      • Stored on disk in flat files so you can use unix command line power tools to bulk maintain pages.
      • thus Mirrorable
      • See lyx's www-* svn
      • See lyx's RSS feeds
      • Active, monthly/quarterly new releases for the last 5 years
      • Translations status looks nice
    • Disadvantages:
      • All skins look somewhat old-fashioned to me (MN)
      • Install by hand as no Debian package
      • Might have a single administrative password for locked pages (ie homepage), so need to investigate how change history is stored (e.g.).


this page is mostly a "It Works!" placeholder, but gives the idea.


  • Sakai
    • It's obviously using one but I'm not sure which one it is
(the page code contains "jQuery.extend(Drupal.settings...")
  • Thunar
    • It's obviously using one but I'm not sure which one it is.
or handcrafted with vi? See last line in source code

New OSGeo Web site