Best practices in using Aurelia KendoUI plugin

This article (Editing Best practices in using Aurelia KendoUI plugin) should be started by writing the instructions for creation of the Area Chart Basic use page (both the view and view-model) as a demonstration of the "algorithm" that is used to decide which control attributes are defined in the View (declarative code) and which are defined in the View-Model. Clearly the datasource attribute is easier to define in the View-Model, but the decision on title is a "toss up" (mater of preference).

This page has only basic declaration:

...
       <collapse-panel title="Basic use" allow-collapse.bind="false">
            <au-au-kendo-chart >

            </au-au-kendo-chart>
        </collapse-panel>
...

I would like to see the "logic" behind the mapping of the KendoUI native attributes definitions and the definitions of the same data in the related Aurelia view-model, including the specifications of strings / integers (I believe that one can only specify strings in the view)

Note:

This article when finished should be merged (in a well defined way) with several existing ones:

1. Component checklist

2. Control Implementation Walkthrough

3. How to build and use aurelia kendoui plugin

4. KendoUI Grid walkthrough

5. Widget Development Guidelines

The whole set should be divided in Plugin Developer Guide and Plugin User Guide with cross links wherever beneficial.