Looks ok. Plan to integrate the developer guides in SCM API and Branch API (plus I have one coming in Credentials API). I want to keep the primary source of that content in the respective project git repos master branch... in asciidoc... you can dance around with converters and sync if you want to!
On Tuesday, 6 December 2016, Daniel Beck <[email protected]> wrote: > Hi everyone, > > I've been working on and off (mostly off) on redoing the Jenkins developer > documentation ('Extend Jenkins' in the wiki) for a while now. > > I just posted my planned new structure for the developer documentation on > the 'docs' list: > > https://groups.google.com/forum/#!topic/jenkinsci-docs/HEQXNzeKV-M > > I'd appreciate feedback on this approach so I actually go in the right > direction with this. > > If you're interested in working with me on filling this with content, or > in reviewing what others write, please let me know. > > Thanks in advance, > Daniel > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:;>. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/FA495E47-8B2D-4FF6-86B3-DF8D764E4511%40beckweb.net. > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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/jenkinsci-dev/CA%2BnPnMy55%3DTAXMm%3DXg%2ByWLqo_rVXWerrQoJgSaSdn%3DfXAQZtqw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
