Also, documentation is almost always written for the beginner, with lots of boiler plate. Which means trying to separate the wheat from the chaffe is quite difficult, and I don't want to read your back ground on "what are containers?" If your software is just like another piece of software, and 18 of the components do the same thing they do in another piece of software, and the 19th is named the same as something else and works completely differently, I'm going to get frustrated if there's no straightforward easy to find explanation.
It’s funny because I usually run into the exact opposite. All documentation seems to be like Unix man pages. It only makes sense if you’re already an expert at it. If you’re not, then it makes no sense and if it does have the answer, you’ll never be able to understand it.
