Hi Steve,
Thanks for the follow-up. I saw similar "documentation not ready" in some libraries I've created, and even that of mbed - making it more awkward to look up the APIs. Having used doxygen in many [offline] projects, I look to that first as the details are better organized than how the source itself may be structured. Without the structure of doxygen, I can imagine the quality of documentation going down.
Having been away for a week, I see in my own libraries that the documentation seems to be there when I rebuild or build docs. And in the mbed library I also see the docs. Thanks for bringing it back.
From my side, I hope you don't remove it - but I'll suggest that informing the users is better than letting it decay. While we're all basically freeloaders on this cloud IDE, I invite others to express their opinion on this subject.
David
Simple steps to repeat this failure -
If an mbed program cannot build the documentation, what chance do I have on a more complex application? And yet the doc's are of high value to users!
mbed team - please turn your attention to a few of these things that used to work 100% reliably and have not been so for some time.