Re: [aerogear-dev] Docs process

Hi David, Preamble: this is still a bit nebulous, but might become a proposal for a docs process: I've got a few examples of mobile.next docs items, and here's the issue 1. Eng want to write specific pieces required by an epic 2. Docs want to publish end-user docs with context, fitting into an overall flow/user story/structure An example is https://github.com/aerogear/mobile-docs/pull/7/files I'm struggling to find context for this piece, but at the same time the guys want to close out the epic. Another example is the readme at https://github.com/aerogear/mi nishift-mobilecore-addon (which will land in mobile-docs as https://github.com/finp/mobile -docs/blob/AEROGEAR-1982/getting-started/minishift_install.adoc) Given this: * I don't want to block eng * I don't want to 'light' review material * some docs have a life outside of mobile-docs repo I'm thinking of the following procedure: 1. Write your docs in the repo of choice (and merge, eg finishing epic) 2. I'll create a placeholder in mobile-docs for that doc , eg mobile-docs/services/metrics-single-auth-provider.adoc with a reference to the source material (in code repo) 3. Create a follow up task to 'create upstream doc and reconcile with code repo' The idea being that eventually, the doc in the code repo is equivalent to mobile-docs repo, but that becomes async, not depending on me to sort everything out to satisfy some epic closure pressure. Obviously, this is not ideal, because developer has moved on by the time I'm reviewing doc, but not everything will require as much context filling as https://github.com/aerogear/mobile-docs/pull/7/files WDYT? Paul -- Paul Wright Mobile Docs (github: finp)