docs(documentation): Add component type to configuration page

Author: RandomByte

internal/documentation/docs/pages/Configuration.md

@@ -19,7 +19,7 @@ See the list of [clients](https://github.com/redhat-developer/yaml-language-serv
 
 ```yaml
 specVersion: "5.0"
-type: application|library|theme-library|module
+type: component|application|library|theme-library|module
 metadata:
   name: some.project.name
 ```
@@ -29,12 +29,17 @@ metadata:
 ### Specification Version and -Type
 A project must define a specification version (`specVersion`), to which its configuration is compatible to. Also see [Specification Versions](#specification-versions).
 
-In addition, a project must define a `type`. This can be either `application`, `library`, `theme-library` (since Specification Version 1.1), or `module`.
+In addition, a project must define a `type`. This can be either `component`, `application`, `library`, `theme-library` (since Specification Version 1.1), or `module`.
 
 The type defines the default path mappings and build tasks. See [UI5 Builder: Types](./Builder.md#types) for details.
 
 :::code-group Example
 
+```yaml [component]
+specVersion: "5.0"
+type: component
+```
+
 ```yaml [application]
 specVersion: "5.0"
 type: application
@@ -125,7 +130,7 @@ resources:
       webapp: webapp
 ```
 
-#### Libraries
+#### Libraries and Components
 - `src`: Mapped to runtime path `/resources`
 - `test`: Mapped to runtime path `/test-resources`
 
@@ -275,6 +280,21 @@ Projects that use the OpenUI5 framework cannot depend on projects that use the S
 
 ::: code-group Example
 
+```yaml [component]
+specVersion: "5.0"
+type: component
+metadata:
+  name: my.company.app
+framework:
+  name: OpenUI5
+  version: 1.82.0
+  libraries:
+    - name: sap.ui.core
+    - name: sap.m
+    - name: sap.ui.table
+    - name: themelib_sap_fiori_3
+```
+
 ```yaml [application]
 specVersion: "5.0"
 type: application
@@ -377,7 +397,7 @@ builder:
       - "/resources/my/project/namespace/test/**"
 ```
 
-```yaml [library or theme-library]
+```yaml [component / library / theme-library]
 builder:
   resources:
     excludes:
@@ -431,13 +451,13 @@ By default, the generated cachebuster info file signatures are based on timestam
 
 ### Component Preload Generation
 
-For projects of type `application` a `Component-preload.js` bundle is generated by default. This bundle will contain most UI5 runtime-relevant resources of the component.  
+For projects of type `application` and `component` a `Component-preload.js` bundle is generated by default. This bundle will contain most UI5 runtime-relevant resources of the component.  
 You can override this default behavior by defining a `componentPreload` configuration.
 
 For projects of type `library`, no Component Preload is created by default.  
 However you can define a `componentPreload` configuration to create Component Preload bundles. Those will be created in addition to the `library-preload.js` bundle.
 
-There are two ways to define the set of components for which preload bundles should be generated. You can either provide `paths` (allowing patterns) or `namespaces`. You can also combine both configuration options. Defining any of them overrides the default preload bundle generation for the root component of `application` projects.
+There are two ways to define the set of components for which preload bundles should be generated. You can either provide `paths` (allowing patterns) or `namespaces`. You can also combine both configuration options. Defining any of them overrides the default preload bundle generation for the root component of the project.
 
 #### paths
 
@@ -600,7 +620,7 @@ This configuration can be overwritten more precisely with the CLI parameters `--
 
 ### Minification
 
-For projects of types `application` and `library`, minification is done for all JavaScript files. During the minification step debug variants are created, original resources are minified, and source maps are created. You can exclude the resources of a project from minification using a list of glob patterns. Matching resources won't be minified, and no debug variants or source maps will be created.
+For projects of types `application`, `component` and `library`, minification is done for all JavaScript files. During the minification step debug variants are created, original resources are minified, and source maps are created. You can exclude the resources of a project from minification using a list of glob patterns. Matching resources won't be minified, and no debug variants or source maps will be created.
 
 The project's `ui5.yaml` file can contain a list of modules declared as glob patterns (resource name patterns) that are excluded from resource minification. Re-includes have to be marked with a leading exclamation mark `!`; see the example below. The order of filters is relevant; a later inclusion overrides an earlier exclusion, and vice versa.