Skip to content

Commit c113380

Browse files
committed
docs: some intro docs to test docs release
1 parent 3337f04 commit c113380

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/src/content/docs/getting-started/introduction.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ sidebar:
1010
The project is kick-started by [Chau](https://github.com/nartc) along with [Enea](https://twitter.com/Enea_Jahollari) and it is fully [open-sourced](https://github.com/nartc/ngxtension-platform). We welcome contributions of all kinds. If you have an issue or idea, please [let us know](https://github.com/nartc/ngxtension-platform/issues/new)
1111
Find yourself adding something over and over again to every Angular projects? That is something we want to have in `ngxtension`. We intend for `ngxtension` to be "_anything goes_" but with careful consideration as well as up-to-standard Angular code so that `ngxtension` can become a one-stop shop for every Angular developer out there.
1212

13+
Once a feature from Angular core resembles a feature from `ngxtension`, we will start the deprecation process for that feature in `ngxtension` and eventually remove it in future major releases. This is a **win** as `ngxtension` has served its purpose of filling the gap.
14+
1315
## Bundle-size Consideration
1416

1517
The library is entirely consisted of [Secondary Entry Point](https://angular.dev/tools/libraries/angular-package-format#entrypoints-and-code-splitting). Even though we ship `ngxtension` as one package (so it is easy for consumers to install), Angular build pipeline should handle code-splitting and tree-shaking properly for all the entry points that `ngxtension` comes with.

0 commit comments

Comments
 (0)