[docs] Remove docs/design.md

[mx-psi]

I think we should remove docs/design.md in favor of the docs in opentelemetry.io.

The document is outdated in some regards (connectors), does not receive a lot of traffic (the only page within the top 10 pages by traffic in this repo within docs/ is the troubleshooting page) and information in this document is already covered on https://opentelemetry.io/docs/collector/configuration and https://opentelemetry.io/docs/collector/deployment.

I would like @open-telemetry/docs-approvers to chime in here and give us their opinion.

[mx-psi]

cc @bogdandrutu @tigrannajaryan @songy23 since you were involved in creating this doc, in case you think it's worth keeping in some form

[svrnm]

I am all in for having this on the website, since those are mostly end-user specific information. We have some of that on the website already, but some details / diagrams could make the existing docs better.

@mhausenblas @theletterf please take a look as well

[mhausenblas]

Agreed with @svrnm!

[tigrannajaryan]

but some details / diagrams could make the existing docs better.

+1 to this. The docs/design.md has diagrams that https://opentelemetry.io/docs/collector/configuration does not. I find the diagrams helpful for understanding.

[mx-psi]

Filed open-telemetry/opentelemetry.io/issues/3547 to move the diagrams

[theletterf]

Agree with moving this documentation. Do we support Mermaid diagrams or similar in OpenTelemetry.io? I'm tempted to add it to Docsy otherwise.

[svrnm]

Agree with moving this documentation. Do we support Mermaid diagrams or similar in OpenTelemetry.io? I'm tempted to add it to Docsy otherwise.

Mermaid is supported on opentelemetry.io yes, e.g. https://github.com/open-telemetry/opentelemetry.io/blob/main/content/en/docs/demo/architecture.md

[cartermp]

Specifically, I think this can be a top-level doc under the collector folder, perhaps just called architecture. We can then merge in/remove content either as a part of that PR or later.

[mhausenblas]

Specifically, I think this can be a top-level doc under the collector folder, perhaps just called architecture. We can then merge in/remove content either as a part of that PR or later.

+1 to docs/collector/architecture and maybe (in terms of left-hand side menu) right before "Building a custom collector"? Also, we should set clear expectations who the target audience is.

[lavishpal]

Could you assign this issue to me ?