Define relevant getting started/next steps for Browser JS

[mydea]

SDK

JavaScript SDK

Description

Assumption: this will be to follow the existing pattern of onboarding in docs. And the aim is to optimize. While there is also a discussion of quickstart vs getting started. That is an orthogonal discussion.

We want to look at JavaScript Browser SDK, and related (react, angular, vue, etc) to find ways to improve the docs experience, and ultimately get people to use more of the Sentry product, and importantly understand and appreciate the value of the products they have adopted.

Below we will list what products and features we are interested in, and prioritize them accordingly.

Suggested Solution

Traditional steps:

1. Install
2. Configure

• should consider the list below of products and features, how much of that can we tastefully and succinctly include?

3. Verify

• ideally this step can include to verify a set of the products and features ie error attached to a trace which can be seen in our issues and tracing product

These steps prioritize that the developer get's to a value add state and confirmation that things are working as soon as possible.

• there is a discussion if this jepoardizes the product learnng experience, for an in product conlcusion. This is related to the above referenced discussion howeever.
• for now we have success metrics around time to send first error, and similar

Products and features:

• Errors
  • Source Maps
• Tracing
  • Distributed tracing
  • Performance and Insights
  • Profiling
• Releases
  • example
  • we provide an overwhelming amount of text here, to say, please set it in the init or we try to do it automatically....it enables XYZ
• Session replay
• User Feedback

Products not listed but relevant, we have never included them in SDK onboarding:

• alerts
• dashboards

SDK Features:

• Configuration
  • Basic options: example debug:true
  • Integrations: importantly what is auto and not, and what is going to
    Enriching Events
  • tags (tags, attributes, context, data (we need to make some decisions here))
  • scrubbing data? no details but a decenst final next step type thing
  • Tree Shaking

Tunneling: this is something where we are currently considering investing more effort as something which could deliver a lot of cusotmer value, but the docs experience today is not great. Related: #11524

User Stories:

Can do if valuable