Add ecosystem section (#2185)

Author: chalin

.github/CODEOWNERS

@@ -30,5 +30,5 @@ content/en/docs/instrumentation/rust/  @open-telemetry/docs-approvers @open-tele
 content/en/docs/instrumentation/swift/  @open-telemetry/docs-approvers @open-telemetry/swift-maintainers @open-telemetry/swift-approvers
 content/en/docs/k8s-operator		@open-telemetry/operator-approvers @open-telemetry/operator-maintainers
 content/en/blog/                         @open-telemetry/docs-approvers @open-telemetry/blog-approvers
-content/en/community/demo/		@open-telemetry/demo-approvers @open-telemetry/demo-maintainers
 content/en/community/end-user/		@open-telemetry/end-user-wg
+content/en/ecosystem/demo/		@open-telemetry/demo-approvers @open-telemetry/demo-maintainers

content/en/_index.md

@@ -14,7 +14,7 @@ developer_note:
 <div class="l-primary-buttons mt-5">
 
 - [Learn more](/docs/concepts/)
-- [Try the demo](/community/demo/)
+- [Try the demo](/ecosystem/demo/)
 
 </div>
 
@@ -57,10 +57,10 @@ Installation and integration can be as simple as a few lines of code.
 
 {{% /blocks/feature %}}
 
-{{% blocks/feature icon="fab fa-github" title="Open Source, Vendor Neutral" url="https://github.com/open-telemetry"%}}
+{{% blocks/feature icon="fab fa-github" title="Open Source, Vendor Neutral" %}}
 
 100% Free and Open Source, OpenTelemetry is adopted and supported by
-[industry leaders](/vendors) in the observability space.
+[industry leaders](/ecosystem/vendors/) in the observability space.
 
 {{% /blocks/feature %}}
 

content/en/blog/2022/troubleshooting-nodejs.md

@@ -364,7 +364,7 @@ distributions can save you time and effort:
 - Up to date with latest OpenTelemetry versions
 - Implementing best practices and avoiding the pitfalls mentioned above
 
-For a list of OpenTelemetry vendors, see [Vendors](/vendors/).
+For a list of OpenTelemetry vendors, see [Vendors](/ecosystem/vendors/).
 
 _A version of this article was [originally posted][] on the Aspecto blog._
 

content/en/community/_index.md

@@ -20,8 +20,7 @@ improve our workflow and more easily manage a community project. [Read
 more](https://github.com/open-telemetry/community#special-interest-groups) from
 our [community repo](https://github.com/open-telemetry/community).
 
-## Open Source Collaboration
+## Ecosystem
 
-OpenTelemetry collaborates and integrates with other open source projects
-including Fluent Bit, Jaeger, Kubernetes, Prometheus, OpenMetrics, and W3C.
-[Read more](/integrations/).
+Looking for components, examples, integrations and more? See
+[Ecosystem](/ecosystem).

content/en/docs/_index.md

@@ -10,7 +10,7 @@ for instrumenting, generating, collecting, and exporting telemetry data such as
 [traces](concepts/observability-primer/#distributed-traces),
 [metrics](concepts/observability-primer/#reliability--metrics),
 [logs](concepts/observability-primer/#logs). As an industry-standard it is
-[natively supported by a number of vendors](/vendors).
+[natively supported by a number of vendors](/ecosystem/vendors/).
 
 ![OpenTelemetry Reference Architecture](/img/otel_diagram.png)
 

content/en/docs/concepts/distributions.md

@@ -39,16 +39,16 @@ Distributions would broadly fall into the following categories:
   instrumentation libraries or vendor exporters not upstreamed to the
   OpenTelemetry project.
 - **"Minus":** These distributions provide a reduced set of functionality from
-  upstream. Examples of this would include the removal of 
+  upstream. Examples of this would include the removal of
   instrumentation libraries or receivers/processors/exporters/extensions found
   in the OpenTelemetry Collector project. These distributions may be provided to
   increase supportability and security considerations.
 
 ## Who would create a distribution?
 
-Anyone could create a distribution. Today, several [vendors](../../../vendors)
+Anyone could create a distribution. Today, several [vendors](/ecosystem/vendors/)
 offer distributions. In addition, end-users may consider creating a distribution
-if they wish to use components in the [Registry](../../../registry) that are not
+if they wish to use components in the [Registry](/registry) that are not
 upstreamed to the OpenTelemetry project.
 
 ## Contribution or distribution?

content/en/docs/concepts/instrumenting.md

@@ -113,9 +113,9 @@ as a proxy or sidecar to your service instances or run on a separate host. The
 Collector can then be configured to forward and export this data to your choice
 of analysis tools.
 
-In addition to open source tools such as Jaeger or Prometheus, a growing list of
-companies support ingesting telemetry data from OpenTelemetry. Please see
-[this page](/vendors) for more details.
+In addition to open-source tools such as Jaeger or Prometheus, a growing list of
+companies support ingesting telemetry data from OpenTelemetry. For details, see
+[Vendors](/ecosystem/vendors/).
 
 [automatic instrumentation]:
   /docs/reference/specification/glossary/#automatic-instrumentation

content/en/docs/concepts/what-is-opentelemetry.md

@@ -70,7 +70,7 @@ Observability back-end (i.e. open source or commercial vendor).
 ## What can OpenTelemetry do for me?
 
 OTel has broad industry support and adoption from cloud providers,
-[vendors](/vendors) and end users. It provides you with:
+[vendors](/ecosystem/vendors/) and end users. It provides you with:
 
 - A single, vendor-agnostic instrumentation library
   [per language](/docs/instrumentation) with support for both automatic and

content/en/docs/getting-started/_index.md

@@ -11,6 +11,6 @@ OpenTelemetry looks like.
 
 If none of the roles below are applicable to you, [let us know][]!
 
-[opentelemetry demo]: /community/demo
+[opentelemetry demo]: /ecosystem/demo/
 [let us know]:
   https://github.com/open-telemetry/opentelemetry.io/issues/new?title=Add%20a%20new%20persona:%20My%20Persona&body=Provide%20a%20description%20of%20your%20role%20and%20responsibilities%20and%20what%20your%20observability%20goals%20are

content/en/docs/getting-started/demo.md

@@ -1,6 +1,6 @@
 ---
 title: Demo
-manualLink: /community/demo/
+manualLink: /ecosystem/demo/
 _build: { render: link }
 weight: 5
 ---