No apologies needed. Leo is terrific, but it does have quite a learning curve. In the end, I think many people end up with their own personalized workflows, most likely with some customized scripts to help.
I like your suggestions of user scenarios walkthroughs, and I think they don't really belong is the New User's Guide but in a collection of such walkthroughs. In the draft outline of the Guide, I do have a subtree of "How Do I ..." topics, but they won't be to the depth you are talking about. Also, probably no one person has the knowledge to handle all common scenarios. If you have one or two of these kind of user scenarios of your own that you'd like suggestions for, try airing them here and maybe we can be of some help (and then the results can be collected into a scenario collection). Leo is especially good for Sphinx documents written in ReST, BTW. I can help with that one. And for the code base scenario, Leo manages its own code base, which is in the LeoPyRef.leo outline (available from the *File* menu), and you can look at that to get ideas. It's on GitHub, so it's clonable. I myself have brought an existing Python project into Leo and put it on GitHub, so I can speak to that, if you are interested in doing that. On Thursday, May 18, 2023 at 11:17:52 AM UTC-4 Ben Hancock wrote: > Thomas writes: > > I've been thinking that there should be a book on Leo. I don't think I've > got another book left in me, but I'm not completely happy with the existing > docs because I don't think they really match what a new user faces when > trying to fire up Leo and use it the first few times. > > > I'm a new Leo user -- I've been programming in Python for 5+ years, but > somehow only recently managed to discover it -- and think something like > this would be very helpful. The tutorials, documentation, and Edward's > YouTube videos are great. But what I think might be really useful are some > step-by-step examples of common user stories. > > For example: > > * I'm a developer working on a small-ish Python project that I collaborate > on with other people. How can I effectively use Leo to start editing my > existing code base? How should I go about breaking up parts of the existing > code into an outline (without actually breaking things)? > > * I'm a technical writer working on a publication. How can I start writing > my outline in Leo, and then save/export it to be shared with others in a > plain text format (ReST, Markdown, etc.)? > > * I manage a small website that's mostly just HTML and CSS. How can I use > Leo's outlining framework to keep things more manageable and reduce > duplication? > > Those are just some ideas. And I apologize in advance if these things > *should* be obvious to a newcomer. I've climbed a few text editor hills > (vim, Emacs, acme, etc.) and I really like what I've seen of Leo, but I do > find myself puzzling at what seem like basic questions. > > Thanks all. > > Ben > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b6fc5193-8b80-407f-a2e5-1fccf0d81463n%40googlegroups.com.
