Documentation for opentelemetry.io

[bobstrecansky]

We'd like to add some documentation to the opentelemetry.io website.

the website_docs folder pushes all of its contents to https://opentelemetry.io/docs/php/

We should include our documentation in there in order to make it easier for end users to adopt our library.

[chalin]

The docs might move: for details, see #423. /cc @austinlparker

[bobstrecansky]

Yes! I think we could use a lot more documentation. That documentation is built here:
https://github.com/open-telemetry/opentelemetry-php/blob/main/website_docs/getting-started.md
Our documentation is unorganized and not complete. Using other languages as a template would probably help a lot.

[chalin]

Yes! I think we could use a lot more documentation.

Great. It would help enormously if the PHP docs were in the website repo. Note that other SIGs have made the choice to move their docs to the website repo since we last exchanged on the topic in September, including:

• Java: Move Java docs into this repo opentelemetry.io#989
• Python: Migrate Python docs to this repo opentelemetry.io#1109 -- still in progress

@cartermp has been driving much of the documentation improvement efforts across languages, and it is much easier for him to do so when the docs are in the website repo before he starts reworking and enhancing the docs. Might you be willing to reconsider your decision for #423

/cc @austinlparker

[bobstrecansky]

@yuktea mentioned she would like to work on this.

[chalin]

Thanks @yuktea! Maybe the best would be to coordinate with @cartermp, who has a better idea of what work needs to be done, unless you (@bobstrecansky et all) have specific pages you'd like @yuktea to start working on?

@yuktea - by the way, the website/communications team meets every other week. For details, see our Meeting doc. Our next meeting is on March 10.

[yuktea]

Thanks @yuktea! Maybe the best would be to coordinate with @cartermp, who has a better idea of what work needs to be done, unless you (@bobstrecansky et all) have specific pages you'd like @yuktea to start working on?

@yuktea - by the way, the website/communications team meets every other week. For details, see our Meeting doc. Our next meeting is on March 10.

Yes, I'll coordinate with them 👍

[tidal]

Closing this issue in favor of #758 , since the website docs are not maintained in this repo anymore.