feat(ng-pixijs): first version

first version

BREAKING CHANGE: first version

Author: klerick

apps/example-ng-pixijs/ng-doc/pages/add-default-pixijs-primitive/index.md

@@ -2,7 +2,7 @@
 keyword: AddDefaultPixijsPrimitivePage
 ---
 
-**NgPixiJS** - provide several component which allow work with PixiJs primitive in Angular way:
+**NgPixiJS** - provides several components that allow working with PixiJs primitive in Angular way:
 
 
 ```typescript
@@ -16,10 +16,10 @@ export interface HTMLElementTagNameMap {
   'pixi-graphics': Graphics;
 }
 ```
-These primitives you can use in your stages components:
+The following primitives you can use in your stage components:
 
 > **Warning**
-> There shouldn't be **HTML** components!!!
+> They shouldn't be **HTML** components!!!
 
 
 

apps/example-ng-pixijs/ng-doc/pages/create-scene/index.md

@@ -8,7 +8,7 @@ To create a scene using PixiJS within your Angular application, you can utilize
 Import the `PixiSceneComponent` into the Angular component where you want to create your PixiJS scene.
 
 > **Note**
-> When using Angular's server-side rendering (SSR), it's important to add [ngSkipHydration](https://angular.dev/guide/hydration#how-to-skip-hydration-for-particular-components) to prevent server-side rendering of components that require direct access to browser APIs, like those using PixiJS.
+> When using Angular's server-side rendering (SSR), it's important to add [ngSkipHydration](https://angular.dev/guide/hydration#how-to-skip-hydration-for-particular-components) to prevent server-side rendering for the components that require direct access to browser APIs, like those using PixiJS.
 
 ```typescript group="create-scene" file="../../../src/app/example-doc/scene/scene.component.ts" name="scene.component.ts" 
 

apps/example-ng-pixijs/ng-doc/pages/create-stage-component/index.md

@@ -2,12 +2,12 @@
 keyword: CreateStageComponentPage
 ---
 
-To add a stage in PixiJS within your Angular application, you will work with the stage property of the [Application](https://pixijs.download/release/docs/app.Application.html#stage) class. 
-A PixiJS stage is essentially a container that holds all the display objects (sprites, graphics, etc.) that you want to render. 
+To add a stage in PixiJS within your Angular application, you will need to work with the stage property of the [Application](https://pixijs.download/release/docs/app.Application.html#stage) class. 
+A PixiJS stage is essentially a container that holds all display objects (sprites, graphics, etc.) that you want to render. 
 In this setup, you can have multiple stages, each represented by an Angular component.
 
 > **Note**
-> Ensure that add [**CUSTOM_ELEMENTS_SCHEMA**](https://angular.dev/guide/components/advanced-configuration#custom-element-schemas) to the component's schemas.
+> Ensure to add [**CUSTOM_ELEMENTS_SCHEMA**](https://angular.dev/guide/components/advanced-configuration#custom-element-schemas) to the component's schemas.
 
 The stage property of the Application class can be used to manage multiple stages. 
 Each Angular component can represent a separate stage, allowing you to modularize and organize your PixiJS application effectively.

apps/example-ng-pixijs/ng-doc/pages/custom-ng-pixijs-component/index.md

@@ -2,8 +2,8 @@
 keyword: CreateCustomNgPixiJSComponentPage
 ---
 
-You can add additional [container](https://pixijs.download/release/docs/scene.Container.html) component and use it in inside of stage or other container component.
-You can add your owner providers. The template can be empty or contain other **NgPixiJS** component
+You can add additional [container](https://pixijs.download/release/docs/scene.Container.html) component and use it inside of stage or other container component.
+You can add your own providers. The template can be empty or contain other **NgPixiJS** component
 ```typescript group="additional-contayner" name="app-some-contayner.component.ts"
 import { PixiContainer } from '@klerick/ng-pixijs';
 import { Container } from 'pixi.js';
@@ -21,8 +21,8 @@ export class AppSomeContaynerComponent extends PixiComponent<Container> {
 }
 ```
 
-You can create your owner primitive with custom logic and use PixiJs primitive as base. This type of component must not contain a template. 
-So, because you need to use a [@Directive](https://angular.dev/api/core/Directive)
+You can create your own primitive with the custom logic and use PixiJs primitive as basis. This type of component must not contain a template. 
+So, because of this you need to use a [@Directive](https://angular.dev/api/core/Directive)
 
 
 ```typescript group="additional-contayner" name="app-some-contayner.component.ts"
@@ -39,10 +39,10 @@ export class AppSomeRectDirective extends PixiComponent<Graphics>{
 }
 ```
 
-`PixiComponent<T extend Container>` - has several additional lifecycle hooks and properties
+`PixiComponent<T extend Container>` - has several additional lifecycle hooks and properties.
 
-**onPixiInit** - This callback is used after init pixijs application. You should implement interface `OnPixiInit`
+**onPixiInit** - This callback is used after initialization of PixiJS application. You should implement interface `OnPixiInit`
 **onRender** - This callback is used when the container is [rendered](https://pixijs.download/release/docs/scene.Container.html#onRender).
 
-**pixiApp** - This property contain instance of [Application](https://pixijs.download/release/docs/app.Application.html)
-**pixiElement** - This property contain instance of base class
+**pixiApp** - This property contains the instance of [Application](https://pixijs.download/release/docs/app.Application.html)
+**pixiElement** - This property contains the instance of base class

apps/example-ng-pixijs/ng-doc/pages/what-is-ng-pixijs/index.md

@@ -8,7 +8,7 @@ By utilizing a custom [RendererFactory2](https://angular.dev/api/core/RendererFa
 #### Key Features
 
 1. PixiJS Integration in Angular:
-  - Enables the use of standard primitives and features of PixiJS within an Angular application, ensuring smooth integration and interaction between the two frameworks.
+  - Enables the utilization of standard primitives and features of PixiJS within an Angular application, ensuring smooth integration and interaction between the two frameworks.
 
 2. Custom RendererFactory2:
   - Implements a custom RendererFactory2 that manages the rendering of the PixiJS scene. This allows developers to use PixiJS for creating complex graphics and animations while staying within the Angular ecosystem.
@@ -17,7 +17,7 @@ By utilizing a custom [RendererFactory2](https://angular.dev/api/core/RendererFa
   - Provides the ability to define custom Angular components that act as wrappers for PixiJS objects. This allows using Angular's component and template approach to manage graphics.
 
 4. Support for Dependency Injection (DI):
-  - Full support for Angular DI within components, simplifying state management and interactions between components based on PixiJS.
+  - Full support for Angular DI within components, simplifing state management and interactions between components based on PixiJS.
 
 5. Control Flow in Templates:
   - Support for Angular control flow directives in templates, enabling the use of constructs like *ngIf, *ngFor, and others for dynamically managing elements in the PixiJS scene.

apps/example-ng-pixijs/public/favicon.ico

@@ -6,7 +6,7 @@
         <h1 ng-doc-text>
 
           Use PixiJS in Angular way</h1>
-        <p class="description" ng-doc-text>PixiJS primitives as Angular components!</p>
+        <p class="description" ng-doc-text>PixiJS primitives as Angular components</p>
         <div class="greeting-buttons">
           <a [rounded]="true" [routerLink]="['docs']" ng-doc-button-flat size="large">
             <span ng-doc-text>
@@ -15,17 +15,17 @@ <h1 ng-doc-text>
           </a>
         </div>
         <div class="greeting-shields">
-          <a href="https://www.npmjs.com/package/@ng-doc/builder" target="_blank">
-            <img src="https://img.shields.io/npm/v/@ng-doc/builder.svg?style=for-the-badge" />
+          <a href="https://www.npmjs.com/package/@klerick/ng-pixijs" target="_blank">
+            <img src="https://img.shields.io/npm/v/@klerick/ng-pixijs.svg?style=for-the-badge" />
           </a>
 
-          <a href="https://github.com/ng-doc/ng-doc/stargazers" target="_blank">
-            <img src="https://img.shields.io/github/stars/ng-doc/ng-doc?style=for-the-badge" />
+          <a href="https://github.com/klerick/ng-pixijs/stargazers" target="_blank">
+            <img src="https://img.shields.io/github/stars/klerick/ng-pixijs?style=for-the-badge" />
           </a>
 
-          <a href="https://github.com/ng-doc/ng-doc/blob/main/LICENSE" target="_blank">
+          <a href="https://github.com/klerick/ng-pixijs/blob/main/LICENSE" target="_blank">
             <img
-              src="https://img.shields.io/github/license/ng-doc/ng-doc.svg?style=for-the-badge" />
+              src="https://img.shields.io/github/license/klerick/ng-pixijs.svg?style=for-the-badge" />
           </a>
         </div>
       </div>