Science Pipelines Docs Meeting 2017-02-09

• Not clear this has a solved answer currently, but we will adopt the tentative idea that documentarians will be mailed whenever major code portions are completed - e.g. the close of stories or epics, and will then check to see if the docs are up to date with the current code
• We will also want examples to be in the CI flow, and whenever they break from code updates, this will immediately trigger editing of them, and potentially the example documentation as well

• Perhaps there can be a higher level page links to the Framework docs
• In Python Usage section: maybe there can be links for this instead
• Another thing is we could add Task badge / sfp page badges so folks know where they are in the docs structure. Kind of like labels for these pages.  

-→ Tdl- Let’s put placeholder comments in the rst files for where links would be

When writing text, then we just need to thinking where reader wants to go.  Should be resistance to linking to a page written a dif style than your section

(This was for changing where `command line task`_ goes to, in procCcd)

• Put in double quotes and dbticks (double backticks) for strings

• Just dbticks for #’s

sbticks (single backticks): will be interpreted as the 'default role' in rst, which links to python objs

dbticks: interpreted as code literal – i.e. monospace