I quite like Thomas&#39; idea of packets for specific org mode uses.  As a starting list consdier: writing for the web, writing for print, basic task management, &quot;full&quot; GTD, time tracking, code/LaTeX tangling. The list could obviously be edited down or up in length.  Each of these packets might include Thomas&#39; list (relevant .emacs code, sample org document, tutorial document and a screencast.)  <br>

<br>It&#39;s true that org is in some ways very simple (remember the &#39;taskpaper&#39; discussion of a year ago?), for basic outlining. But it&#39;s also true that the minimal code-and-knowhow needed to do some of the specific tasks which org has proven so good at it can be a fair hurdle for a beginner to put together.  In this respect the raw flexibility of org-mode (exactly like Emacs itself) has its down side.  We might be able to lower the getting-started hurdle if we were able to tell people; &quot;You want to do GTD-like task management?  Look &lt;here&gt; and follw the recipe.  You want to outline your writing?  Look &lt;here&gt;.  Heaven knows you can always tweak it later.&quot;  I have often thought that there would be ways to get people up and running even without the venerable Emacs tutorial. <br>

<br>Scot <br><br>