On Thu, 7 Dec 2017 06:30:13 -0600 "Edward K. Ream" <[email protected]> wrote:
> On Wed, Dec 6, 2017 at 5:04 PM, Terry Brown <[email protected]> > wrote: > > > If we use the "open Tip issues are being edited, closed Tip issues > > are ready to use" workflow, we can get the Tips from: > > > > https://api.github.com/repos/leo-editor/leo-editor/issues? > > labels=Tip&state=closed > > > > It's a JSON list of dicts which have a `body` key (they ripped that > > terminology off Leo, I bet ;-) which is the issue summary markdown. > > ​Hehe. Or we could just cut/paste :-) It would not, in fact, take > very long. I disagree. We need to define the canonical source for the tips, or violate DRY. If we're using GitHub because of its markdown editing / preview, I think by default GitHub is the canonical source. If a tip needs revision (they will), where does that happen? Here's code to harvest them: https://github.com/leo-editor/snippets/blob/master/scripts/misc/get_tips.py It captures the title for feed back, I don't think we'll use it in the user visible tip. Cheers -Terry -- 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.
