Streamline Remix Getting Started Page

Author: onurtemizkan

src/platform-includes/getting-started-config/javascript.remix.mdx

@@ -55,52 +55,16 @@ Sentry.init({
 });
 ```
 
-Initialize Sentry in your entry point for the server to capture exceptions and get performance metrics for your [`action`](https://remix.run/docs/en/v1/api/conventions#action) and [`loader`](https://remix.run/docs/en/v1/api/conventions#loader) functions. You can also initialize Sentry's database integrations, such as Prisma, to get spans for your database calls.
+Initialize Sentry in your entry point for the server to capture exceptions and get performance metrics for your [`action`](https://remix.run/docs/en/v1/api/conventions#action) and [`loader`](https://remix.run/docs/en/v1/api/conventions#loader) functions. You can also initialize Sentry's database integrations, such as <Link to="/platforms/node/performance/database/opt-in/#prisma-orm-integration">Prisma</Link>, to get spans for your database calls.
 
-<SignInNote />
-
-```typescript {filename: entry.server.tsx}
-import { prisma } from "~/db.server";
-
-import * as Sentry from "@sentry/remix";
-
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-  tracesSampleRate: 1,
-  integrations: [new Sentry.Integrations.Prisma({ client: prisma })],
-  // ...
-});
-```
-
-<Note>
-
-Learn more about <Link to="/platforms/node/performance/database/opt-in/#prisma-orm-integration">Sentry's Prisma integration </Link>.
-
-</Note>
+Also, wrap your Remix root with `withSentry` to catch React component errors (Remix v1) and routing transactions.
 
-If you use a custom Express server in your Remix application, you should wrap your [`createRequestHandler` function](https://remix.run/docs/en/v1/other-api/adapter#createrequesthandler) manually with `wrapExpressCreateRequestHandler`. This is not required if you use the built-in Remix App Server.
+<Alert>
 
-<Alert level="info">
-
-`wrapExpressCreateRequestHandler` is available starting with version 7.11.0.
+If you use the Remix `v2_errorBoundary` future flag, you need to configure a [v2 ErrorBoundary](#v2-errorboundary) in addition.
 
 </Alert>
 
-```typescript {filename: server/index.ts}
-import { wrapExpressCreateRequestHandler } from "@sentry/remix";
-import { createRequestHandler } from "@remix-run/express";
-
-// ...
-
-const createSentryRequestHandler =
-  wrapExpressCreateRequestHandler(createRequestHandler);
-
-// Use createSentryRequestHandler like you would with createRequestHandler
-app.all("*", createSentryRequestHandler(/* ... */));
-```
-
-Also, wrap your Remix root with `withSentry` to catch React component errors (Remix v1) and routing transactions. If you use the Remix `v2_errorBoundary` future flag, you need to configure a [v2 ErrorBoundary](#v2-errorboundary) in addition.
-
 ```typescript {filename: root.tsx}
 import {
   Links,
@@ -149,6 +113,29 @@ withSentry(App, {
 });
 ```
 
+## Custom Express Server
+
+If you use a custom Express server in your Remix application, you should wrap your [`createRequestHandler` function](https://remix.run/docs/en/v1/other-api/adapter#createrequesthandler) manually with `wrapExpressCreateRequestHandler`. This is not required if you use the built-in Remix App Server.
+
+<Alert level="info">
+
+`wrapExpressCreateRequestHandler` is available starting with version 7.11.0.
+
+</Alert>
+
+```typescript {filename: server/index.ts}
+import { wrapExpressCreateRequestHandler } from "@sentry/remix";
+import { createRequestHandler } from "@remix-run/express";
+
+// ...
+
+const createSentryRequestHandler =
+  wrapExpressCreateRequestHandler(createRequestHandler);
+
+// Use createSentryRequestHandler like you would with createRequestHandler
+app.all("*", createSentryRequestHandler(/* ... */));
+```
+
 ## Remix v2 features
 
 _Available from SDK version 7.59.0_

src/platform-includes/getting-started-primer/javascript.remix.mdx

@@ -4,12 +4,10 @@ Sentry's Remix SDK enables automatic reporting of errors and exceptions, as well
 
 </Note>
 
-## Features Overview
+Under the hood, Remix SDK relies on our [React SDK](/platforms/javascript/guides/react/) on the frontend and [Node SDK](/platforms/node) on the backend, which makes all features available in those SDKs also available in this SDK.
 
-- [Error Tracking](/product/issues/) with source maps for both JavaScript and TypeScript
-- Events [enriched](/platforms/javascript/guides/remix/enriching-events/context/) with device data
-- [Breadcrumbs](/platforms/javascript/guides/remix/enriching-events/breadcrumbs/) created for outgoing HTTP request with XHR and Fetch, and console logs
-- [Release health](/product/releases/health/) for tracking crash-free users and sessions
-- [Performance Monitoring](/product/performance/) for both the client and server
+<Alert title='Non-Node Support' level='warning'>
 
-Under the hood, Remix SDK relies on our [React SDK](/platforms/javascript/guides/react/) on the frontend and [Node SDK](/platforms/node) on the backend, which makes all features available in those SDKs also available in this SDK.
+Sentry's Remix SDK does not officially support adapters that use non-Node runtimes, such as Cloudflare Workers.
+
+</Alert>

src/platform-includes/getting-started-sourcemaps/javascript.remix.mdx

@@ -0,0 +1,7 @@
+## Add Readable Stack Traces to Errors
+
+The Remix SDK provides a script that automatically creates a release and uploads sourcemaps. To generate sourcemaps with Remix, you need to call remix build with the `--sourcemap` option.
+
+On release, call `sentry-upload-sourcemaps` to upload source maps and create a release. To see more details on how to use the command, call `sentry-upload-sourcemaps --help`.
+
+For more advanced configuration, you can use [`sentry-cli`](https://github.com/getsentry/sentry-cli) directly to upload sourcemaps.