This question is locked. New answers and comments are not allowed.
The Kendo UI documentation is pretty good but providing working code / screenshots of the various UI components would be a big help. I understand that users can override all of the visible attributes of a component via CSS but at least showing the default look and feel would be helpful to developers just starting out with Icenium. I have found myself creating a KendoPlayground app just to create samples of all of the button, listview, etc... features so that I can see what they actually look like. I know that you have some of this functionality demonstrated on the "Kendo UI Demos" but it would be extremely helpful to have this info right on the documentation pages.
For example, the current Kendo UI Mobile "Button" API Reference page only displays the javascript features and you have to go to the associated Getting Started page to see the markup for this component. However, neither of these pages actually show what a button looks like on any of the supported platforms. Also, there is mention of icons usage on the Getting Started page but I have yet to find any mention in these docs about usage of the "km-icon" class or any of the other associated classes that can help a user to control and style the button component.
Kendo UI and the associated MVVM framework is great but I feel that the documentation is lacking for even experienced developers that are new to the framework.
For example, the current Kendo UI Mobile "Button" API Reference page only displays the javascript features and you have to go to the associated Getting Started page to see the markup for this component. However, neither of these pages actually show what a button looks like on any of the supported platforms. Also, there is mention of icons usage on the Getting Started page but I have yet to find any mention in these docs about usage of the "km-icon" class or any of the other associated classes that can help a user to control and style the button component.
Kendo UI and the associated MVVM framework is great but I feel that the documentation is lacking for even experienced developers that are new to the framework.