Repository navigation
Feature Request: Fragment Open Telemetry Documentation on homepage by "User". #4304
Unanswered
jsuereth
asked this question in
Content Refactoring
Replies: 3 comments
|
I think the user/integrator stuff would be great for the new docs section, definitely. I'm going to try to get the new theme out ASAP so we can build content for it. |
0 replies
|
FYI, I just linked this to #770, which will be used to track progress on the IA rework. |
0 replies
|
We have something like that nowadays at https://opentelemetry.io/docs/getting-started/, but I am wondering if this is 100% the same, as this issue also talks about having integrators and maintainers listed (where Dev & Ops are "Users" in this definition). I think we can and should iterate on that. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd really love if the Open Telemetry homepage had the following content:
users,integratorsandmaintainers).Then there'd be a new homepage with geared information and links.
For Users
This would be a section for end-users on how to leverage OT for custom spans/metrics/logging and set-up configure an OT system. It'd be great if basic architectural concerns and links for "how to" on language-level integrations. Effectively this would have:
TL;DR: This is "How/why should I use OT in my app deployments"
For Integrators
This would be a homepage geared towards other projects trying to use OT APIs to provide spans/metrics/logs for their users. This would include:
TL;DR: This would be "How/why should I use OT in my library/framework/service"
For Maintainers
This would be a homepage geared that outlines how to get started contributing and the breadth-scope of the project.
TL;DR: This would be "How to I add features or fix bugs"
Example website splits of this sort:
I'm happy to discuss further ideas and happy to help provide content to address the three use cases.
All reactions