<commit_before><br>

## 1 Introduction
<br>
<br>

The help category named **"About this application"** refers to the **[standalone instance](http://aurelia-ui-toolkits.github.io/demo-kendo)** of the **[embedded sample application](https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin/tree/master/sample)** in the **[Aurelia-KendoUI bridge](https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin)** project.
<br>
<br>

This explanation will make more sense after checking the information in the category **About KendoUI bridge**, which explains the overal structure of the Aurelia plugin project which implements KendoUI bridge. Note that we are using the term **bridge** to point out the specific **purpose** of the Aurelia KendoUI plugin project - to implement the Aurelia friendly interface / bridge to KendoUI controls set.
<commit_msg>Improve the definition of this application<commit_after><br>

## 1 Introduction
<br>
<br>
Describing this application in a few words is not a simple task due to its "multiple personalities". It started as an advanced exercise in writing Aurelia Plugin, a basic building block of the whole Aurelia Framework, with the intent to create Aurelia Components from KendoUI controls. This "personality" is encapsulated in **[this Github repository](https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin)**
<br><br>

In order to accelerate the development of this plugin, we decided to use somewhat unusual architecture, where we embedded the application acting as a consumer of the plugin's service into the plugin project itself. This way, each newly added "wrapper" to **[this folder](https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin/tree/master/src)** can immediately be tested in this **[embedded application](https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin/tree/master/sample/src)**.
<br><br>

Having this embedded application in place, it became instantly obvious that it would be very useful if it could be also hosted on Github as an independent application, so we could use the references to the sections of the app and the plugin in the context of the application's on-line help documents. As a result we have this "embeded" application **[here](http://aurelia-ui-toolkits.github.io/demo-kendo)**, with the great feature - it automatically reflects the state of the whole project.
<br><br>

As we started to improve this application's user interface (by using the KendoUI controls that are already available as Aurelia components), it became apparent that calling this application Aurelia-KendoUI components catalog is the best name for the whole project, which can now be seen as the Catalog with an embedded plugin.
<br><br>

The help category named **"About this application"** refers to the **[standalone instance](http://aurelia-ui-toolkits.github.io/demo-kendo)** of the **[embedded sample application](https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin/tree/master/sample)** in the **[Aurelia-KendoUI bridge](https://github.com/aurelia-ui-toolkits/aurelia-kendoui-plugin)** project.
<br>
<br>

This explanation will make more sense after checking the information in the category **Bridge developers tutorials**, which explains the overall structure of the Aurelia plugin project which **implements** the KendoUI bridge. Note that we are using the term **bridge** to point out the specific **purpose** of the Aurelia KendoUI plugin project - to implement the Aurelia friendly interface / bridge to KendoUI controls set.

{'fraction_non_alphanumeric': 0.09152734485689998, 'fraction_numerical': 0.0005667327854916407, 'mean_word_length': 5.31484794275492, 'pattern_counts': {'":': 0, '<': 21, '<?xml version=': 0, '>': 21, 'https://': 7, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5042407', 'n_tokens_mistral': 964, 'n_tokens_neox': 933, 'n_words': 420}