Documentation suggestion

2 posts, 1 answers
  1. Dr.YSG
    Dr.YSG avatar
    210 posts
    Member since:
    Dec 2009

    Posted 25 Apr 2012 Link to this post

    In response to some of my questions, Telerik support staff has been outstanding. They provide samples, and explanations that illuminate a great deal as to what is going on inside the KendoUI, the semantics and syntax of methods, attributes, etc. As well as interactive JSFiddle demonstrations.

    I feel guilty for asking some of these things, but I first pour through the documentation and if I don't find it, then I am forced to ask.

    Suggestion:

    In response to questions that seem to be common and thinly covered in the formal documentation (e.g. aggregation in datasource, grid and charts) consider writing up a TECH NOTE, and then cross linking it to the documentation nodes under Grid, Chart and Datasource.
    In addition, if you create a JSFIDDLE, then also link that to the documentation. (call the link DIVE DEEPER, or something like that).

    That way you will have a permanent record, decrease the customer support costs, and provide us with interactive ways (JSFiddle) to dive deeper than the thin layer of formal documentation. It allow you to leverage your staff support costs by creating a living Knowledge Base. I could even see users submitting well documented JSiddles for Telerik points. (crowd source your documentation and decrease the cost of creating the documentation corpus!).





  2. Answer
    Georgi Tunev
    Admin
    Georgi Tunev avatar
    7207 posts

    Posted 27 Apr 2012 Link to this post

    Hi,

    Thank you for the suggestion - I forwarded them to our Dev team for consideration and updated your points.


    Greetings,
    Georgi Tunev
    the Telerik team
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
  3. Kendo UI is VS 2017 Ready
Back to Top