Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Common weights/structure for language-specific pages #2829

Closed
13 tasks done
svrnm opened this issue Jun 7, 2023 · 6 comments
Closed
13 tasks done

Common weights/structure for language-specific pages #2829

svrnm opened this issue Jun 7, 2023 · 6 comments

Comments

@svrnm
Copy link
Member

svrnm commented Jun 7, 2023

As discussed during the SIG meeting 05/22/23 we want to have a common structure for all language navigations:

  • 10 Getting Started
  • 20 Automatic
    • 10 Configuration
    • 20 Extensions
    • ...
  • 30 Instrumentation (updated Jan 2024)
  • 40 Libraries
  • 50 Exporters
  • 60 (Context) Propagation
  • 70 Resources
  • 80 Sampling
  • 100-200 language specific docs
  • 210 API (external link)
  • 220 Examples (external link)

I added the weights after the discussion to make it consistent through that

this also is going to fix #2431

TODO:

@chalin
Copy link
Contributor

chalin commented Jun 7, 2023

My only suggestion would be to start language-specific pages at 100 instead of 90.
Otherwise, great initiative, thanks!

@svrnm
Copy link
Member Author

svrnm commented Jun 7, 2023

My only suggestion would be to start language-specific pages at 100 instead of 90. Otherwise, great initiative, thanks!

good call, let me fix some of my PRs then ;-)

@svrnm
Copy link
Member Author

svrnm commented Jun 7, 2023

@chalin , what do we need to do to get the latest updates for the go pages, since open-telemetry/opentelemetry-go#4211 got merged?

@chalin
Copy link
Contributor

chalin commented Jun 7, 2023

@svrnm - refresh the Go submodule by running this command:

npm run update:submodule -- content-modules/opentelemetry-go

and submit the update as a PR.

@svrnm
Copy link
Member Author

svrnm commented Jun 9, 2023

Thanks @chalin , then #2849 will do it

@chalin
Copy link
Contributor

chalin commented Jun 9, 2023

Closed by #2849

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants