<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 17/06/15 22:56, andre wrote:<br>
</div>
<blockquote cite="mid:5581ED26.4020608@andrecastro.info" type="cite">
<pre wrap="">It lends itself to a number of editing and publishing workflow, and organizational structure.</pre>
</blockquote>
<br>
I wonder, do any of you feel that FM has a specific workflow? I have
written 3 (and a bit) books now, I worked with Mick on two of them,
and I feel that there is something really core to FM about workflow.
Trying to condense this might be helpful. From my perceptive the FM
method:<br>
<br>
<ul>
<li>It's results in something quite linear</li>
<li>The beginning should be super simple - an overview of basic
functionality, orientation style.<br>
</li>
<li>The main chapters should be structured by day to day USE of
software and the building of skills, using real life examples
often.<br>
</li>
<li>We can assume that installation was done by someone else, esp
if a web-app, and put that at the end with advanced chapters.<br>
</li>
<li>Not a single step should be skipped - every click needed
should be noted</li>
<li>The language should be relaxed, clear to second-language
English speakers (avoid metaphores) </li>
</ul>
<p>a<br>
x<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Share the phpList love!
Twitter: @phpList
Facebook: facebook.com/phpList</pre>
</body>
</html>