-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(perf): Restructure performance getting started #2121
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
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sentry/sentry-docs/r4nqc9f2g/sentry.dev |
PeloWriter
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor edits. Thank you.
Co-authored-by: Fiona <[email protected]>
High level goals
Remove the dropdown in https://docs.sentry.io/product/performance/getting-started/ (because users get very confused) in favour of a list of links. Doing this also means that the getting started pages are all unified (error getting started and performance getting started for each SDK).
Each link in that list should reference performance specific documentation under that SDK platform
Make sure that all the pages have links at the bottom so that users can easily navigate between different sections
Make sure performance set up is unified across languages
Roughly:
tracesSampleRateThis also came up because if we add
Angularto the getting started dropdown, it replacesBrowser JavaScriptas the first thing rendered, which I don't think is ideal.WIP: