Talk:Web site: Difference between revisions
Jump to navigation
Jump to search
(Created page with '== PmWiki == * from the [http://thread.gmane.org/gmane.comp.gis.grass.devel/40095 mailing list]: <pre> re CMS for Grass I saw www.lyx.org the other day and thought it looked good…') |
(→PmWiki) |
||
| Line 12: | Line 12: | ||
libhtml-wikiconverter-pmwiki-perl | libhtml-wikiconverter-pmwiki-perl | ||
It's stored on disk in flat files (ie you can ues unix command | |||
line power tools to bulk maintain pages) | line power tools to bulk maintain pages) so easy to mirror and | ||
perhaps even keep in SVN if we wanted. It seems to me that | |||
the home-portal doesn't really need to run more than about a | the home-portal doesn't really need to run more than about a | ||
dozen pages of content- it's just a front end reception service. | dozen pages of content- it's just a front end reception service. | ||
Revision as of 15:15, 8 July 2010
PmWiki
- from the mailing list:
re CMS for Grass I saw www.lyx.org the other day and thought it looked good for our 'portal' front page needs. Aesthics are not too austere flat text like trac wiki, not too blog or wiki like either. Actually it uses PmWiki but the visitors don't know that, the login button is very subtle. and they kept notes! http://www.lyx.org/SiteDocumentation http://www.pmwiki.org convert html -> pmwiki libhtml-wikiconverter-pmwiki-perl It's stored on disk in flat files (ie you can ues unix command line power tools to bulk maintain pages) so easy to mirror and perhaps even keep in SVN if we wanted. It seems to me that the home-portal doesn't really need to run more than about a dozen pages of content- it's just a front end reception service. No idea about RSS support, but we can't be the first folks to think about it. Again, https logins and reuse of osgeo ids+ access groups would be a bonus.