Size: 1421
Comment: Added a link to Frockle wiki and shuffled some things around.
|
Size: 1506
Comment: Expanding to WebLearn hierarchy (but still keeping to 3 levels!).
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
==== Content ==== * [wiki:self:WebLearnDevelopment Development] - index page of topics relating to WebLearn development issues. |
==== Development topics ==== * --([wiki:self:WebLearnDevelopment Development] - index page of topics relating to WebLearn development issues.)-- * [wiki:Self:WebLearn/CopyUI WebLearn/CopyUI] copyUI stuff. |
Line 11: | Line 12: |
~-''My hunch is that flat hierarchies with the content here are inherently a 'good thing'. Therefore as a general rule I'd suggest adding pages in this area prefixed with WebLearn. Only when a given topic gets too big should sub-pages be created for it. This is what I've done with the topic WebLearnCopyUI anyway! - Hmmm..., I'm not quite sure what exactly I was thinking when I first wrote this(!) Sure, we probably want something like no more than 3 levels, but why didn't I just arrange my own example as WebLearn/CopyUI (it's only one more '/' character in the URL after all!).''-~ | --(~-''My hunch is that flat hierarchies with the content here are inherently a 'good thing'. Therefore as a general rule I'd suggest adding pages in this area prefixed with WebLearn. Only when a given topic gets too big should sub-pages be created for it. This is what I've done with the topic WebLearnCopyUI anyway! - Hmmm..., I'm not quite sure what exactly I was thinking when I first wrote this(!) Sure, we probably want something like no more than 3 levels, but why didn't I just arrange my own example as WebLearn/CopyUI (it's only one more '/' character in the URL after all!).''-~)-- |
WebLearn
Introduction
Welcome to this wiki which is an area intended to discuss [http://www.weblearn.ox.ac.uk WebLearn] development issues. Write access is only available to members of LTG / the VLE team, but read access is completely open to the public.
Development topics
[wiki:self:WebLearnDevelopment Development] - index page of topics relating to WebLearn development issues.
[wiki:WebLearn/CopyUI WebLearn/CopyUI] copyUI stuff.
Links
[https://wiki.oucs.ox.ac.uk/weblearn/ Restricted WebLearn Wiki] if you have an Oxford WebAuth account you may be able to access this wiki where WebLearn issues are discussed in more of a "closed" manner.
[wiki:self:../Frockle Frockle] - this is a JISC Toolkit & Demonstrator 2007 project, which intends to integrate friend-of-a-friend (FOAF) type functionality into WebLearn.
NOTES:
My hunch is that flat hierarchies with the content here are inherently a 'good thing'. Therefore as a general rule I'd suggest adding pages in this area prefixed with WebLearn. Only when a given topic gets too big should sub-pages be created for it. This is what I've done with the topic WebLearnCopyUI anyway! - Hmmm..., I'm not quite sure what exactly I was thinking when I first wrote this(!) Sure, we probably want something like no more than 3 levels, but why didn't I just arrange my own example as WebLearn/CopyUI (it's only one more '/' character in the URL after all!).