Changes between Version 7 and Version 8 of TutorialsTNG

Timestamp:

Apr 7, 2017 5:53:48 AM (8 years ago)

Author:

smk78

Comment:

—

TutorialsTNG

@@ -29 +29 @@
 == The Bigger Picture ==
 Any tutorials we produce will be ''part'' of a bigger portfolio of 'documentation' comprising:
+
 * the in-program '''Help''' (actually called 'Documentation' in !SasView itself) - this is invariably the first place any Sasview User looks for answers
 * the '''Tutorials''' themselves
 * the !SasView [http://www.sasview.org Website] - which has a good FAQ page created from actual questions from Users & links to other resources
-* the !SasView [http://trac.sasview.org TRAC] site - primarily for the Development Team, but a lot of content should be accessible to advanced Users
+* the !SasView [http://trac.sasview.org TRAC] site - primarily for the Development Team, but a lot of content should be accessible to 'advanced' Users
+
 Whilst there will be some cross-over between these different strands they should ''not'' seek to duplicate material unnecessarily.
 
-== So what is a Tutorial? ==
-A Tutorial is self-paced instruction that provides a step-by-step approach to some learning unit. They should be interactive, visual (and/or audio), goal-driven, and provide some form of feedback (such as through question-answer exercises). This definition therefore potentially encompasses a wide range of delivery mechanisms. 
+== So What Is A Tutorial? ==
+A Tutorial is self-paced instruction that provides a step-by-step approach to some learning unit.
 
+It should be interactive, visual (and/or possibly audio), goal-driven, and provide some form of feedback or test of learning (such as through question-answer exercises and/or providing access to comparative results).
+
+== The Need For A Philosophy ==
+The problem with the Tutorial definition above is that it potentially encompasses a wide range of delivery mechanisms. Within the !SasView project we are, of necessity (given our available resources), going to need to focus on providing the key material in the most accessible form. That means Tutorial ''documents'' in HTML, PDF, and possibly (since the production overhead should essentially be zero given the first two) eBook formats.
+
+Anything else simply cannot be a priority for us at the moment. It could, however, be provided by the Community if they so wished...
+
+If we agree that we shall provide some Tutorial ''documents'' then, to ease production, maximise buy-in, and encourage Community contributions, we need a production platform that is ''free''(!), intuitive (ie, WYSIWYG), and suitable for version control using TRAC. (The current Tutorial is written in Microsoft Powerpoint which only meets two of these criteria).
+
+After looking around Andrew identified two possibilities:
+
+* 
+* 
+
+