After considerable thought, I am going to adopt Lewis Neal's suggested installation docs <https://groups.google.com/d/msg/leo-editor/cel28Tw2OMU/2fPo809EBQAJ> myself. I'll add them to LeoDocs.leo and update Leo's web site accordingly. This should happen later today. We can then discuss them here, in this thread.
*Aha*: outline structure (in LeoDocs.leo or in the online TOC) clarifies the issues *for me* enough so that I can proceed. *Example* The rest of this post discusses Matt's excellent PyPi instructions, which he added to LeoDocs.leo. You could call this part an Engineering Notebook entry. Feel free to ignore. The main problem I had was with a section I called "Optional: Test with TestPyPI". Don't remember what the original headline was. It was a child of the node "Build & publish a release". Should this node be a child or should it follow the "Build & publish" node? There was a problem either way. Logically, testing would seem to follow building. Otoh, this item was "subsidiary" because it was optional. And testing could be called part of the build process. I finally saw that the real resolution to this dilemma was to rename the node to "Not recommended: Test with TestPyPI". Now it doesn't much matter so much *where* the node goes, because the "Not recommended" label is much stronger than the "Optional" prefix. I chose *not* to make this node a child node, because I wanted to emphasize the step-by-step nature of the recipe. *Summary* Outline structure is the best overall guide. This structure can then suggest wording improvements that sidestep structure-related dilemmas. 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.
