Thanks for this list @RHL!
You have my assurances that this is a given. The information architecture of LSST DM, to this point, is a little horrendous. The New Docs will absolutely have a unified architecture that is logical and easy to follow. Right now there are so many hidden corner’s in DM’s documentation that it’s completely impossible to expect anyone from the community to reliably discover any piece of information about our work. Note that a lot of this will happen by pulling information out of Confluence and doxygen and unifying them in a single doc platform.
I’ve also grown to appreciate the usefulness of the Design Documents as part of my reStructuredText conversion exercise. I’d love to have all the Design Documents available as websites, and organized about a Design Document Library. Since everything will be HTML, it will be easy for the Stack Docs, and other resources, to deeply link into the Design Docs.
I think this work will involve overhauling http://dm.lsst.org and making it an integral part of the Stack experience.
Okay, so this seems to be the most wanted fundamental document. I’ll happily make this a priority.
Yes, as a Stack Newbie I’ve found the existing developer documentation to have lots of holes and worrying deprecation warnings. I do plan to make a Developer Workflow Guide a priority.
Aside from user guides for Tasks and Measurement Algorithms, it seems that a lot of the other priorities, at least as posed here, seem to be best framed as tutorials. In that case it may be worth it for me to put together at least one tutorial to establish the format, and then invite the rest of DM to contribute more tutorials.
That’s a terrific resource. It seems that Steve’s docs are organized around recipes/tutorials, and I’ll look into seeing what could be forked and repackaged into tutorials for the New Docs.
But keep in mind that tutorials and recipes are just one aspect of the New Docs; the New Docs also needs to user guides that explain stack concepts and architectures, and include API references (what we’ve used doxygen for in the Old Docs.)
I think the best/only way to migrate this sort of content onto Community is to have people re-ask relevant questions and have others re-answer them. You could make it a hack day exercise.