docs: add component authoring documentation

<!-- markdownlint-disable MD041 -->

Adds comprehensive documentation for component authoring with the new OCM CLI:

**New reference pages:**
- `reference/component-constructor.md` — field reference for `component-constructor.yaml`, the input format for `ocm add cv`
- `reference/component-descriptor.md` — field reference for the component descriptor output format (v2 schema)
- `reference/input-and-access-types.md` — field-level reference for all supported input types (`dir`, `file`, `helm/v1`, `utf8`) and access types (`OCIImage`, `localBlob`, `OCIImageLayer`, `Helm`)

**New how-to and tutorial:**
- `how-to/model-products.md` — step-by-step guide for modeling multi-component products with component references
- `tutorials/advanced-component-constructor.md` — tutorial covering multi-component constructors, labels, sources, and nesting patterns

**Replaced outdated content:**
- Removed `tutorials/complex-component-structure-deployment.md` (replaced by `model-products.md`)
- Removed `tutorials/component-descriptor-example.md` (replaced by `component-descriptor.md` reference)
- Moved and rewrote `tutorials/input-and-access-types.md` as a reference page, removing types not supported by the new OCM (`binary`, `docker`, `dockermulti`, `ociImage`, `spiff`, `gitHub`, `npm`, `s3`, `wget`)

<!--
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

Fixes: open-component-model/ocm-project#889

Signed-off-by: Piotr Janik <piotr.janik@sap.com>

Author: piotrjanik

content/docs/getting-started/create-component-version.md

@@ -480,4 +480,4 @@ ocm get cv ghcr.io/open-component-model/ocm//ocm.software/ocmcli:0.35.0 --recurs
 
 ## Related Documentation
 
-- [Tutorial: Input and Access Types]({{< relref "input-and-access-types.md" >}}) - Explore all supported resource types and how to use them
+- [Reference: Input and Access Types]({{< relref "docs/reference/input-and-access-types.md" >}}) - Explore all supported resource types and how to use them

content/docs/how-to/model-products.md

@@ -10,15 +10,17 @@ Enterprise software products rarely ship as a single artifact. They are assemble
 
 This guide shows you how to use OCM component references to create a **versioned bill of materials (BOM)** for a multi-component product, giving your organization a single source of truth for every release.
 
-## You'll end up with
+## Goal
+
+{{< callout type="note" >}}
+**You will end up with**
 
 - A `component-constructor.yaml` that defines service components and a product-level aggregator
-- Component references that pin exact, QA-approved version combinations
+- Component references that pin exact version combinations
 - A portable [CTF archive]({{< relref "docs/concepts/transfer-concept.md#common-transport-format-ctf" >}}) ready for transfer across registries and air-gapped environments
+{{< /callout >}}
 
-## Estimated time
-
-~15 minutes
+**Estimated time:** ~15 minutes
 
 ## How it works
 
@@ -36,7 +38,7 @@ A product component uses [`componentReferences`](https://github.com/open-compone
 - [OCM CLI]({{< relref "ocm-cli-installation.md" >}}) installed
 - Familiarity with [the component constructor]({{< relref "../tutorials/advanced-component-constructor.md" >}})
 
-## Define the Components
+## Steps
 
 {{< steps >}}
 {{< step >}}
@@ -134,8 +136,6 @@ Each parent component declares `componentReferences` entries that point to its c
 
 > **Note:** `component-constructor.yaml` is the default filename the CLI looks for when no `--constructor` flag is given. The examples below omit the flag because the file uses the default name. If your file has a different name or location, pass `--constructor <path>` explicitly.
 
-
-
 {{< steps >}}
 {{< step >}}
 

content/docs/reference/component-constructor.md

@@ -6,9 +6,9 @@ weight: 11
 toc: true
 ---
 
-The component constructor is a YAML file that describes one or more component versions and their artifacts. It is the input for the `ocm add cv` command, which builds component versions into a [Common Transport Format (CTF)](https://github.com/open-component-model/ocm-spec/blob/main/doc/04-extensions/03-storage-backends/ctf.md) archive.
+The component constructor is a YAML file that describes one or more component versions and their artifacts.
 
-**Schema:** [`configuration-schema.yaml`](https://ocm.software/schemas/configuration-schema.yaml) (JSON Schema)
+**Schema:** [`schema-2020-12.json`](https://github.com/open-component-model/open-component-model/blob/main/bindings/go/constructor/spec/v1/resources/schema-2020-12.json) (JSON Schema 2020-12)
 
 ## Top-Level Structure
 
@@ -107,7 +107,7 @@ resources:
 | `name` | string | yes | Name of the resource. |
 | `type` | string | yes | Type of the resource. See [Artifact Types](#artifact-types). |
 | `access` | object | yes | Access specification for the resource. See [Access Types](#access-types). |
-| `version` | string | yes | Version of the resource (relaxed semver). |
+| `version` | string | no | Version of the resource (relaxed semver). Defaults to the component version. |
 | `relation` | string | no | Relation of the resource to the component (`local` or `external`). Default: `external`. |
 | `extraIdentity` | object | no | Additional identity attributes for the resource. |
 | `labels` | array | no | Labels associated with the resource. |

content/docs/reference/component-descriptor.md

@@ -6,7 +6,7 @@ weight: 12
 toc: true
 ---
 
-The component descriptor is a YAML document that formally describes a component version. It is the central data structure of the Open Component Model. Every component version stored in a [component repository](https://github.com/open-component-model/ocm-spec/blob/main/doc/01-model/01-model.md#repositories) is represented by exactly one component descriptor.
+The component descriptor is a YAML document that formally describes a component version. It is the central data structure of the Open Component Model. Every component version stored in a [component repository](https://github.com/open-component-model/ocm-spec/blob/main/doc/01-model/01-model.md#component-repositories) is represented by exactly one component descriptor.
 
 **Schema:** [Open Component Model v2 schema](https://github.com/open-component-model/open-component-model/blob/main/bindings/go/descriptor/v2/resources/schema-2020-12.json) (JSON Schema)
 

content/docs/reference/input-and-access-types.md

@@ -27,6 +27,7 @@ Embeds a directory as a tar archive.
 | `compress` | boolean | no | Compress the tar archive (gzip). |
 | `reproducible` | boolean | no | Normalize file attributes (timestamps, permissions) for reproducible digests. Recommended when signing. |
 | `preserveDir` | boolean | no | Include the directory itself in the archive. |
+| `followSymlinks` | boolean | no | Include the content of symbolic links in the archive. Not yet implemented; accepted for compatibility with previous OCM versions. |
 | `excludeFiles` | array of string | no | Glob patterns for files to exclude. |
 | `includeFiles` | array of string | no | Glob patterns for files to include. |
 

content/docs/tutorials/configure-resolvers.md

@@ -332,7 +332,7 @@ Now that you know how to configure resolvers, you can:
   registries, Helm repositories, and more
 - [Creating a Component Version]({{< relref "docs/getting-started/create-component-version.md" >}}) — Build component
   versions and work with CTF archives
-- [Input and Access Types]({{< relref "input-and-access-types.md" >}}) — Reference for resource input types (by value)
+- [Input and Access Types]({{< relref "docs/reference/input-and-access-types.md" >}}) — Reference for resource input types (by value)
   and access types (by reference)
 - [Signing and Verification]({{< relref "signing-and-verification.md" >}}) — Sign and verify component versions with
   cryptographic keys