For example, customer/developer wants to use RadMaskedInput
Ok, he opens TDN =telerik developers network library(kind of MSDN library) url and reads all instructions, etc...
Project is compiled, released and is in production....
After some time developer decided to upgrade libs to the latest version (could be few Rad releases in between)... He reads release notes for current build, nothing suspicios there, a lot of stuff fixed. Cool !!!
Ok , dll's replaced, project hopefully builds, but during run time something goes wrong (different behaviour, for example RadGrid RowActivation event or RadMaskedInput Text property)...
Now, only one way to find what wrong is - find somewhere release notes, try to find what was changed and when..
But instead it would be nice if open documentation for trouble control, and have section: release notes history. There you could put what was changed/added, when. Release history could be long - either last few years or all releases.
In this case developer can see that something was changed in "trouble" control without looking at release note for whole library, where only changed controls mentioned and link to each control's release note provided (info could be duplicated in main release note as well).
Something like this -).
Now one more small improvement suggestion. In http://www.telerik.com/help/silverlight/
would be nice to have left panel in independent frame with scroll, same as MSDN classic view left panel. In MSDN click on a link keeps left selected branch active, and you don't need to scroll whole page to find tree branch again.
In case of Telerik, lets say you see documentation for controls which are on the very bottom of the tree (RadWindow or RadZip). Click on any link refreshes page and you have to scroll to very buttom again to find where you were.
If would be nice if left panel is not updated.
Anyway, hard to explain, easier to show -)) look at msdn lib (classic view) to see difference.