Well, I posted them as examples of documentation format (HTML, rather than .chm), layout/organization and content. The reason I used Stripe and Braintree as examples is because they are open and thus can be linked here, not because they are representative of what I am looking for in terms of openness. In other words, I don't expect the LF SDK docs to be openly accessible for everyone.

It would be great, for example, if the SDK docs were also html files that opened in the browser, and they had a modern layout (maybe with Bootstrap or something), and each function/method had clear examples and discussed various use cases and common gotchas, and explained various responses you can get from the server and what that response means.

For example, when I send a POST request to https://stripe.com/docs/api#create_customer I know exactly how the request should be structured and what type of response to expect. I also know what types of scenarios might lead to errors. With .chm files this information is very difficult to glean if one is not already familiar with the SDK. They are also lacking in detail. For example, methods tell you what the parameters are and what the return type is, but its very very barebones (probably because most of it was auto-generated from the code comments).