docs: Add guide for creating OTel Input Packages

docs/extend/index.md

@@ -15,6 +15,10 @@ Begin by understanding what is an [integration](./what-is-an-integration.md).
 
 Dive deep into the technical aspects of building integrations with Elastic products. Our [Building Integrations](./build-new-integration.md) guide covers everything from architecture and design principles to coding best practices and sample projects.
 
+## OTel Input Packages
+
+Learn how to create [OTel Input Packages](./otel-input-packages.md) that configure OpenTelemetry Collector receivers within EDOT (Elastic Distribution of OpenTelemetry).
+
 ## Testing and Validation
 
 Ensure your integrations work seamlessly by following our [Testing and Validation](./testing-validation.md) guidelines. Learn about different testing methodologies, tools, and techniques to validate your integration's performance and reliability.

docs/extend/integration-definitions.md

@@ -36,6 +36,8 @@ Unlike integrations, content packages do not include data streams or Agent polic
 
 An input package is a type of package that exposes the raw configuration of an Elastic Agent input for custom use cases. Unlike integrations that provide pre-configured data collection for specific technologies, input packages allow users to configure inputs directly for their unique requirements.
 
+A special type of input package is the **OTel Input Package**, which configures OpenTelemetry Collector receivers within EDOT (Elastic Distribution of OpenTelemetry). See [OTel Input Packages](./otel-input-packages.md) for details on creating these packages.
+
 
 ## Data stream [_data_stream]