I think what you said about the "over the shoulder" concept of learning is potentially the most powerful way to bring people up to speed. Some people will still prefer traditional "read the docs" style documentation but many will prefer narrated "demo.py" style demos showing them *exactly* what Leo is capable of.
I believe YouTube is the best place host these demos as it offers the "playback speed" setting which in my experience has been critical to me watching any technical/instructive videos. On Saturday, February 11, 2017 at 5:44:59 PM UTC-5, Edward K. Ream wrote: > > Here is the first draft for a new intro to Leo's tutorials, Leo in 5 > minutes. Let me know what you think. > > *Outlines* > > Leo is a full-featured outliner and IDE, with features borrowed from emacs > and vim. When Leo reloads an outline, it remembers where you left off. > > Outlines consists of *nodes *with *headlines* and *bodies*. The *outline > pane* shows nodes. The *body pane* contains the body of the selected node. > > *External files* > > - @file trees in the outline represent *external files* on your file > system. Leo *updates @file nodes* when you change external files outside > of Leo. > > - When saving an outline, Leo writes all changed @file trees to their > external files. > > *Scripting and markup* > > - Leo's *markup language* consists of`@others` and `<< sections >>`. > Markup controls how Leo writes @file trees to external files. > > - Any outline node can contain a python script. Three *predefined symbols* > give Leo scripts *easy *access to all the structure and data in the > outline. > > - The same markup applies to scripts as well as external files. Before > executing a script node, Leo *composes *the script from the script node > and (depending on markup) some or all of its descendants. > > - @button nodes contain scripts that *can be applied to other nodes*. > > *Clones* > > - Outline nodes can be *cloned*. Cloned nodes are actually the *same *node, > but they appear in different places in the outline. *Changes to any clone > affect all other clones of that node, including their descendants*. > Clones are a powerful organizing tool. > > - Leo's *clone-find* commands create clones of all found nodes. The > clone-find commands move the newly-created clones so they are all children > of an organizer node describing the search. > > *Summary* > > @file nodes create external files. Guided by markup, Leo writes @file > trees to external files. Leo updates @file trees when external files change > outside Leo. Leo's importers create outlines from external files. > > Leo composes complex scripts from a node and (depending on markup) some or > all of its descendants. Leo scripts have access to all data in the outline, > including its structure. > > Clones are nodes that appear in multiples places within the outline. Leo's > clone-find commands gather found nodes together in one place. > > *Ironic Comments* > > The "less said the better" principle has allowed me, *for the first time > ever*, to summarize Leo's essential an unique features in just a few > words. This summary probably seems pretty clear to Leonistas. However, I > wonder how much newbies will understand. > > There are two ways forward. > > 1. Explain the pithy summary above using *text* examples, including text > representations of Leo's outline structure. We must do this for the written > docs, but text only hints at Leo's dynamic nature. > > 2. Use this post as a preliminary script for a demo, eventually to appear > on YouTube. I'll attempt this soon. > > Your comments and suggestions, please. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
