>From the Leading-The-Horse-To-Water Dept:* Moving ahead with the switch to the new documentation, one next step is to deprecate the docs in the wiki. This will ensure that people will know what is (hopefully) current and what isn't.
The pages in question are those in the GEOSDOC space [1]. This includes the current User Guide and Developer Guide. Other pages, such as the homepage and anything in the GEOS space [2] will be unaffected. So how to do this? Apparently, Confluence isn't excellent at theming just a single space. I was thinking that adding a warning box to the top of each page with a message pointing in the right direction might be a better way to go. If so, maybe (fingers crossed), it might be possible to script insert some Wiki Markup to the head of each page, via the database. Arne, do you know if such a think would be possible? Some examples of what I was thinking are here [3]. Please feel free to comment. What would you like to see that is intrusive enough to be noticed, but not intrusive enough to be irritating? :) [1] http://geoserver.org/display/GEOSDOC [2] http://geoserver.org/display/GEOS [3] http://geoserver.org/display/~bmmpxf/Deprecation * Apologies to slashdot Thanks, Mike Pumphrey OpenGeo - http://opengeo.org ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
