docs(sentry-basics): Consolidate tutorials into one getting-started tutorial#18709
docs(sentry-basics): Consolidate tutorials into one getting-started tutorial#18709coolguyzone wants to merge 16 commits into
Conversation
Merge the distributed-tracing, integrate-frontend, and integrate-backend tutorials into a single JS-only getting-started tutorial. The three overlapping tutorials were outdated and duplicated setup steps; this replaces them with one cohesive flow (React frontend + Express backend) covering project creation, SDK setup, distributed tracing, source maps, and suspect commits. - Add 7 pages under docs/product/sentry-basics/getting-started-tutorial/, with the source maps step updated for Vite and the backend for ESM - Delete the old integrate-frontend/ and integrate-backend/ tutorials - Add redirects from all old URLs to their new homes - Repoint inbound links across docs and featureInfo.tsx - Mark source maps and suspect commits as optional; add a ~60 min time estimate and a Seer entry in What's Next - Refresh Arcade IDs; hide outdated Arcades pending recapture Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Make the "Enable Readable Stack Traces" page work for a new developer and fix the auth-token setup that didn't actually work with Vite. - Store the auth token in .env.sentry-build-plugin (the file the Sentry Vite plugin auto-loads) instead of a plain .env, which Vite does not load into process.env; drop the non-working authToken config line - Spell out how to find the org and project slugs in the Sentry UI - Warn that the source-map project must match the DSN's project - Add a screenshot of the readable frontend stack trace Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the stale Create React App screenshot with the modernized storefront, and give the image descriptive alt text. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The suspect commits + stack trace linking step required installing the GitHub integration (which can need org-owner approval) plus a multi-part setup — too involved for a getting-started tutorial. Remove it as a hands-on step and surface the feature (and Seer) as "go further" links in the wrap-up instead. - Delete configure-suspect-commits.mdx (former step 6) - Move the What's Next wrap-up onto the source-maps page; add a suspect commits / GitHub integration link and reword the Seer entry - Update the step list, drop the suspect-commits capability bullet, and lower the time estimate to ~45 min - Repoint the integrate-frontend/configure-scms redirect to the GitHub integration docs Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a "Step 2 of 5" orientation line and wrap the sub-steps in <StepConnector checkable> so readers can track completion. Applied to the frontend SDK page first to preview the look before rolling out. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Apply the "Step X of 5" indicator and <StepConnector checkable> rail to the remaining step pages (create-new-project, initialize-sentry-sdk-backend, generate-first-error, enable-readable-stack-traces) so all five steps have consistent progress affordances. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Switch the step pages from <StepConnector checkable> to the numbered, non-checkable form used by the platform onboarding pages. Drops the checkbox/Reset control that rendered without the accompanying rail. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The StepConnector rail didn't render its numbered circles on the tutorial pages (only the checkbox/reset control showed). Remove it from all step pages and keep the simple "Step X of 5" counter for orientation; restore the manual sub-step numbering on the section headings. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a TutorialProgress component: a slim track that fills with Sentry purple in proportion to step/total, with a minimal purple bug icon riding the tip of the fill. Place it under the "Step X of 5" counter on each of the five step pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Cap the bar at ~1/3 of the content width and give the bug a bold dark outline (plus slightly thicker legs/antennae) so it stands out. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Render a flattened, legs-splayed "squashed" bug variant when step === total, so the bug that's been riding the progress bar gets squashed at the finish. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the squashed-bug variant with a small purple headstone reading "RIP / BUGS" (two lines) shown when step === total. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Revert the final-step tombstone/squashed variant; the progress bar shows the upright bug at every step for now. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
||
| 1. Log in to your [Sentry organization](https://sentry.io). | ||
|
|
||
| 1. Select **Projects** from the organization icon menu. | ||
| 1. Select **Projects** from the left side navigation menu. |
There was a problem hiding this comment.
| 1. Select **Projects** from the left side navigation menu. | |
| 1. Click on your organization's icon in the top left navigation, and select **Projects** from the menu. |
There was a problem hiding this comment.
I think this instruction is also handy above in the FE tutorial. It talks a good deal about the DSN, but not to copy it or keep it handy. I haven't used it yet in my setup, I've only created these two projects in Sentry.io.
| 1. Clone the forked repository to your local environment: | ||
|
|
||
| ```bash | ||
| git clone git@github.com:<your_username>/tracing-tutorial-frontend.git |
There was a problem hiding this comment.
I didn't have SSH set up, so this failed. Maybe say, "if you already have SSH set up, use git clone git@github.com:<your_username>/tracing-tutorial-frontend.git
Otherwise use `git clone https://github.com/<your_username>/tracing-tutorial-frontend.git" ?
| 1. Clone the forked repository to your local environment: | ||
|
|
||
| ```bash | ||
| git clone git@github.com:<your_username>/tracing-tutorial-backend.git |
There was a problem hiding this comment.
Same as in the FE. Maybe also suggest using git clone https://github.com/<your_username>/tracing-tutorial-backend.git in case SSH isn't set up.
Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
…-project.mdx Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
…-sentry-sdk-frontend.mdx Co-authored-by: Shannon Anahata <shannon.anahata@gmail.com>
|
@coolguyzone I think there might be a malformed part of the backend files. I couldn't get Sentry to initialize the way it was set up, and this was the recommended change in In package.json update to: I have a PR open for that change now. |
|
|
||
| 1. In the **root** of the `tracing-tutorial-frontend` folder (the same folder that contains `package.json`), create a new file named exactly `.env.sentry-build-plugin` — including the leading dot. | ||
|
|
||
| 1. Add your auth token to the file, replacing `___ORG_AUTH_TOKEN___` with the token you generated above: |
| pnpm preview | ||
| ``` | ||
|
|
||
| 3. Open the app (make sure the backend is still running on `http://localhost:3001`), open your browser's dev console, and perform an "Empty Cache and Hard Reload" so the new build is served. Then trigger the cross-project error again by clicking the **Nonfat Water** button. |
There was a problem hiding this comment.
| 3. Open the app (make sure the backend is still running on `http://localhost:3001`), open your browser's dev console, and perform an "Empty Cache and Hard Reload" so the new build is served. Then trigger the cross-project error again by clicking the **Nonfat Water** button. | |
| 3. Open the app (make sure the backend is still running on `http://localhost:3001`), open your browser's dev console, and right-click the reload button, then select 'Empty Cache and Hard Reload' so the new build is served. Then trigger the cross-project error again by clicking the **Nonfat Water** button. |
| 2. Serve the production build: | ||
|
|
||
| ```bash {tabTitle:npm} | ||
| npm run preview | ||
| ``` |
There was a problem hiding this comment.
Looks like, by default, vite preview serves on port 4173. Should be noted.
There was a problem hiding this comment.
Actually, just hardcoded the preview port too in a PR.


DESCRIBE YOUR PR
Consolidates the three overlapping, outdated Sentry Basics tutorials (
distributed-tracing,integrate-frontend,integrate-backend) into a single, cohesive, JS-only getting-started tutorial: create projects → add the SDK to a React frontend and Express backend → capture a distributed-tracing error → (optionally) enable readable stack traces.The two sample apps this tutorial uses were also refreshed in separate repos (Vite + React 19 frontend, ESM Express 5 backend, modernized storefront UI) and are already merged, so all in-doc repo links point at working code.
See https://sentry-docs-git-coolguyzone-feattutorial-update.sentry.dev/product/sentry-basics/getting-started-tutorial/
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
🤖 Generated with Claude Code