Comments:Tutorials

Overview

aims

We must shorten the time for potential co-workers to get info of what they could do!

strategies

Furthermore, we have to divide the Projects into Sub- and Sub-Sub-Projects. Again to shorten the needed time for each contributor.

ideas

  • So lets easy start chronologically with some Install tutorials (You know thats easy nowadays) [But for all 3 systems] (chicken level)
  • How to configure mime (chicken level)
  • then the user has a working dms-c installation which could be productive, for small working groups (collaborative dog)
  • also use dm as a visualization mapping tool with an icon workshop (adventurer)
  • Put in some information/data Interlink it, hide, search. (chicken level)
  • then how to publish and work with others. (collaborative dog)
  • How to use DeepaMehta as email client. (adventurer)
  • Then comes come dev-thingy...[I still don't know about that!] (pioneer stuff, faar away)

Discussion

x28de 14-May-2008 23:59 CEST After Jörg suggested to move some simple issues from HowTo to UsersGuide, I would also like to move some advanced features from Tutorials to HowTo. If I understand it right that "Tutorials" should also contain the Screencasts, then this is what people watch before they even consider to download something or apply for an account.

Two items from the Chicken "level" are, IMO, too advanced for this level:

  • File Handling/ Mime type is the sort of things needed only for the Desktop replacement level,
  • configuring the 'Installation' topic is something I don't understand and don't want to understand.

Instead, I think a simple sandbox example should be imported and explained.

The "pioneer level" should IMO not appear among the user levels but be separately handled in a section for developers. Clearly distinguishing between work above the engine hood and below the engine hood, is essential for users who don't want to get oily hands but rather concentrate on their domain-specific thoughts.


Suggestions:

  • Tutorials section can either contain audiovisual guidance, like Screencasts and interactive demo-challenges at one time but should tag themselves through a more thought-out guidance concept than those within the how to section (those can be quick and dirty ones which could evolve later into the user guide or the tutorials section)
  • then distincton betweensingle chicken and collaborative dog levels are meant: personal usage (importing files, maps and mime/types, drag& drop, export) on one side and the collaborative usage: shared workspaces and personal copies of topic maps as well as roles and the creation of an own shared workspace with uploading and sharing documents this would be like a distinction of tutorials through purpose of use/ scenario of usage
at last i want to say, i would not make the distinction between users and developers within the tutorials, but there is still a long way to walk until we may be clearer on this. Malte 20-May-2008 18:59 CEST
  • x28de 20-May-2008 17:23 CEST "for a better visualization of the information structure": I think this is up to the user themselves. Probably s/he gets it that the shown structure is very imperfect and is s/he is challenged to improve it, and hopefully s/he realizes that many of their own structures in their brain need to be visualized and improved. That was my intent, therefore I chose associations that cannot simply be reduced to tree structures. Specialized topics would came later. But if several topics should be deleted for more clarity, go ahead, I just wanted to provide raw material. Who will invent the screenplay script and write the narration text for the screencast?
  • x28de 20-May-2008 18:13 CEST If someone wants more of a completed visual structure, I uploaded another demo map "etymology.zip" where the associations are typed (mostly "derivation" which is probably the best approximation for "etymological kinship"), and the only question is even simpler: Just one topic needs to be linked and this can be done by "what's related" if not from the description text.
  • --Thilo 21-May-2008 02:37 CEST The order which i mentioned before was not meant to determine the order of presentation in the wiki it was just an my guess for production order. I mean we definitely have to do them all, so the production order isn't that important. For the presentation i like to interlink the tutorials and User Guide and finally, to fulfill the deepamehta paradigm, let the user decide her order.
    • --Thilo 21-May-2008 02:37 CEST To determine the timespan to present each feature i first need some text, but again i think more is better and just lets start with an exact copy of Jörgs User Guide texts, and then improve. I would like to see some faces for intro and outro so that we can introduce some community members. Malte what do you think lets spend a night in some pc-pool (yours or mine?;D)and be collaborative productive. I need a faster PC to record this casts smooth.
    • Malte 21-May-2008 17:31 CEST we could do so, i will see how far i come with the more important things until the weekend and then maybe on monday evening, could be possible. i already had problems setting up the xvid capture stuff on my machine. we`ll see.
      • --Thilo 21-May-2008 20:37 CEST Ok, got a dm install on the pool machine and an working capturer prog. lets do it.

x28de 22-May-2008 00:07 CEST If you need more ideas for tutorials, I have uploaded some, look at this .pps file tutorialvorschlag.pps.

  • --Thilo 22-May-2008 01:07 CEST Yes, i didn't think of this approach for the first projects, but we need to anticipate as many approaches to the matter as possible. There are defiantly people who find exact this order useful. I think there is more stress for us in finding the right form of presentation on the Community-Portal.
    • i would suggest the blog for presentation. we could post an article right at the spot and it would be easy to mashup and spread the word Malte
  • Malte 22-May-2008 12:44 CEST dear matthias, i really like your approach and enjoyed clicking through your tutorial, the text is funny somehow and i would like to produce some raw material guided by this on monday evening in the pcpool at the tu, which thilo already set up. i know we can improve, but while trying we will see and since i am neither soo familiar with screencasts and if dict leo is right, then i would say: "The proof of the pudding is in the eating." within "post production" the story gets its shape. thank you!