utm source added

[aidankmcalister]

Summary by CodeRabbit

• Documentation
  • Updated external links in the Railway deployment guide to include UTM tracking parameters for analytics across Railway, Prisma template, dashboard, and docs destinations.
  • Anchor text and instructional content remain unchanged; only destination URLs were adjusted.
  • No behavioral, code, or runtime impact; the guide’s flow is unaffected and requires no action from users.

[coderabbitai]

Walkthrough

Adds UTM tracking parameters to external links in the Railway deployment MDX page. No changes to prose, structure, or logic. No code or runtime impact.

Changes

Cohort / File(s)	Summary
Docs: add UTM params to external links `content/200-orm/200-prisma-client/500-deployment/101-traditional/325-deploy-to-railway.mdx`	Appends utm_medium=integration, utm_source=docs, utm_campaign=prisma to multiple external URLs (Railway site, template, dashboard, docs). No content or structural edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• DC-5179 Railway docs page #7102 — Introduces the “Deploy to Railway” guide containing this MDX file; this PR updates its external links with UTM parameters.

Suggested reviewers

• nikolasburk
• mhessdev
• ankur-arch

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch railway-docs-link-additions

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

original	preview
content/200-orm/200-prisma-client/500-deployment/101-traditional/325-deploy-to-railway.mdx	content/200-orm/200-prisma-client/500-deployment/101-traditional/325-deploy-to-railway.mdx

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

content/200-orm/200-prisma-client/500-deployment/101-traditional/325-deploy-to-railway.mdx (1)

7-87: Consider centralizing UTM tagging to avoid drift.

If this pattern will be reused across pages, add an MDX component (e.g., ) or a rehype plugin to auto-append UTMs for specific domains to reduce future misses and typos.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 01b9578 and 98187bd.

📒 Files selected for processing (1)

• content/200-orm/200-prisma-client/500-deployment/101-traditional/325-deploy-to-railway.mdx (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: runner / linkspector
• GitHub Check: Check internal links
• GitHub Check: Lost Pixel

🔇 Additional comments (6)

content/200-orm/200-prisma-client/500-deployment/101-traditional/325-deploy-to-railway.mdx (6)

7-7: UTM params added correctly on primary Railway link.

Consistent with the pattern used elsewhere.

---

11-11: UTM params added to template link look good.

Matches medium/source/campaign used above.

---

19-19: Account link UTM looks correct.

Consistent with other links.

---

30-30: Dashboard link UTM looks correct.

Parameters/order consistent.

---

87-87: Docs link UTM looks correct.

Same convention applied to docs.

---

7-87: All Railway links include utm_medium
Verified that no Railway or docs.railway.app URLs without an utm_medium parameter remain in the content/ directory.

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	98187bd
Status:	✅  Deploy successful!
Preview URL:	https://23c51657.docs-51g.pages.dev
Branch Preview URL:	https://railway-docs-link-additions.docs-51g.pages.dev

View logs