I meant the 5 minutes tutorial :-).

On 12/02/17 19:07, Offray Vladimir Luna Cárdenas wrote:

I like the short nature of the tutorial and I don't think they're targeted towards people who already know Leo or are developers, as Rengel said in this thread, except for the parts that introduce Leo in reference to emacs and vi, so would be needed some more explanation to non-developers and add some links to markup languages and expand the introduction of external files. Why they are important in the Leo context? How Leo can help you to (de)construct external files. I agreed with Rengel that defining the target of documentation is important instead of leave them implicit (only developers which are, in some way familiar with Vim and emacs?).

I think that it is important to show examples of the Leo markup and the programmability capabilities of the tree/document. Org mode introduce this for a "general" population with the TODO examples or for a more specific one with literarate devops. At this moment, I'm making the Grafosfocopio manual and my idea is to present generalities of it (installation, outlining, node parts, and special keywords, markdown and PDF export) and use the static PDF manual as an invitation to explore the interactive examples included with the environment. I have found that providing a functionality to update the documentation and the software independently is pretty useful to test both. May be Leo could include a functionality to download the tip version of its documentation, and when makes sense, put demo.py (or demo.leo) there.

Cheers,

Offray


On 12/02/17 06:40, lewis wrote:
*Aha 1*: Think visually.
sounds good

*Aha 2*: Pictures are better than videos.
Supported by clear text examples sounds even better :)

Your recent demo.py plugin markdown document is very well presented, with really nice code formatting. It could benefit enormously from pictures at all the right places.

Lewis
--
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 [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

--
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 [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to