While I love wikis for a great many things, I don’t think this would be the most useful tool for my project. For development, we won’t be using a mass collaboration process, need more structure, and will have a lot of multimedia. For actual delivery, I’ve struggled with the difficulty of doing much that is interactive with MediaWiki.

The import/export functionality of whatever we use would give end consumers the option of putting it in a wiki if they chose though, which I think is important.

While I agree that any LMS imposes structure on end users, our target audience (public school K-12 teachers) are generally not able/willing to spend a lot of time on massaging content. One thing I like a lot about Moodle is that it is very easy for an individual teacher to move things around, add content or resources, take things out, etc.

Also, a lot of schools here already use Moodle. Not having a steep learning curve and supplying vetted content for a tool they already use will be a huge benefit to widescale adoption.

Now, to figure out the logistics of the import/export routine. :)

I’m thinking of a wiki for collaborative authoring of content, with the addition of an extension that would allow exporting of sections of content in a variety of formats, including print (most students in South Africa would have very limited access to the internet). Mediawiki combined with Pediapress seems like it might be useful.

I like your idea of using one system to manage content and then being able to export / import that content into another platform. My only issue with that approach though, is that I disagree with using Learning Management Systems in general. I think that more often than not, they lock users (teachers and students) into a structured system that isn’t flexible enough. But that’s just a personal opinion based more on how LMS’ are actually used, as opposed to how they could be used.