> Actually, I'm not sure about this either. If the release docs remains > as a 20+ page collection of documents, it's a big burden to transfer > these to Drupal, in addition to learning a new system, etc. > Originally I thought it would be a 1 time transfer, and that the next > release would be a copy of the docs in Drupal (which is easy). But I > understand now that really doesn't make sense, as you would want to > enable the community to help update the trunk docs in the wiki before > each release. So in that case, this will be an ongoing big chunk of > work for each new release.
Right, seems like a PIA. > Instead, I'd rather consider how we can change the Docs wiki so that > it's more obvious that you're in a different space, since that seems > to be the main issue. Any ideas on this? At a minimum, we can change > the color scheme, left navigation style, and even the css. Seems like lots of options here. What's the problem, just mass confusion between the two sites? Maybe we should add a bit orange/red footer to the bottom of the developer docs that says: "Development Docs Only. (Release docs here)" But I'm certainly supportive of something a bit more sophisticated... Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
