Our "Getting Started" (landing) pages for the JavaScript SDK docs have grown over time. They are not fully consistent and we want to spend some time to improve them.
This task is somewhat broad, and may consist of various improvements. Part of the issue is to investigate the getting started pages and see what we can do better.
Potential things to do
General structure of what should be on the Getting Started page (template)
How can we explain concepts of things that are covered? E.g. "what is tracing/profiling" and similar questions.
How can we provide good, explorable next steps (e.g. setting up tunneling, ...)
Priority of SDKs
While we eventually want to work on all getting started pages, we want to start with JavaScript, then extend to other platforms later. Inside of JS, we may start with React, Browser (Default, "JavaScript"), Next.js and Express, which cover a good amount of our most important JS platforms.
SDK
JavaScript SDK
Description
Our "Getting Started" (landing) pages for the JavaScript SDK docs have grown over time. They are not fully consistent and we want to spend some time to improve them.
This task is somewhat broad, and may consist of various improvements. Part of the issue is to investigate the getting started pages and see what we can do better.
Potential things to do
Priority of SDKs
While we eventually want to work on all getting started pages, we want to start with JavaScript, then extend to other platforms later. Inside of JS, we may start with React, Browser (Default, "JavaScript"), Next.js and Express, which cover a good amount of our most important JS platforms.
Suggested Solution
No response