Managing tutorial samples

This article documents the process of creating and managing the content described in the section 4. Application Developer tutorialsarrow-up-right from the Aurelia KendoUI Bridge Documentationarrow-up-right

In order to ensure the best possible syncronization between the Aurelia's skeleton navigation samplesarrow-up-right used as the basis for KendoUI bridge's own (parallel) set of KendoUI tutorials codearrow-up-right, the information in 4. Application Developer tutorialsarrow-up-right describes the process of modifying Aurelia samples to be able to use KendoUI bridge.

This article explains the creation and management of the kendoui-tutorials-codearrow-up-right repository which contains the finished code for samples as tutorials in the section 4. Application Developer tutorialsarrow-up-right. The process is very similar for all entries in kendoui-tutorials-codearrow-up-right repository:

Step 1

Copy the code of the original navigation skeleton sample from skeleton-navigationarrow-up-right sample to kendoui-tutorials-codearrow-up-right

Step 2

Transform the original code in just the created kendoui-tutorials-codearrow-up-right repository to add all changes needed to make this sample use KendoUI bridge.

The specifics of each transformation are described on the following pages:

1. KendoUI-skeleton-esnextarrow-up-right

2 KendoUI-skeleton-esnext-aspnetcorearrow-up-right

3. KendoUI-skeleton-esnext-webpackarrow-up-right

4. KendoUI-skeleton-typescriptarrow-up-right

5. KendoUI-skeleton-typescript-aspnetcorearrow-up-right

6. KendoUI-skeleton-typescript-webpackarrow-up-right

Each of the above pages shows what needs to be changed in order to add four additional tabs which render Aurelia KendoUI components. The first two use the KendoUI corearrow-up-right widgets, while the second two use subscription based KendoUI Pro packagearrow-up-right.

Last updated