Skip to content

feat(partners): point Render CTAs at the render.com/tanstack landing page - #1281

Merged
tannerlinsley merged 1 commit into
mainfrom
jonny/render-tanstack-landing
Sep 20, 2026
Merged

tannerlinsley merged 1 commit into
mainfrom
jonny/render-tanstack-landing

Conversation

@jhislop-design

@jhislop-design jhislop-design commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

What

Render built a co-branded landing page for TanStack at render.com/tanstack. This repoints the Render partner page's conversion CTAs to it, keeping the existing UTM parameters (utm_source=tanstack&utm_medium=referral&utm_campaign=gold-launch&utm_content=partner_page).

Follow-up to #1218 (the Render Gold partner page), which is already merged.

Changes

  • RENDER_HREF now points at https://render.com/tanstack?… instead of dashboard.render.com/register. This drives the four primary CTAs: hero "Start free on Render", pricing "Start on the free plan", testimonials "Move your app to Render", and the closing "Deploy your TanStack app".
  • The how-it-works "Deploy on Render" button (previously a dashboard.render.com/select-repo blueprint deep-link) now points at the same landing page. Since both URLs are identical, the separate RENDER_BLUEPRINT_HREF constant is removed.

Deliberately left as-is

  • "See compute pricing" still deep-links to render.com/pricing — its label names that specific page.
  • The footer render.com text-link still points at the canonical home — the visible link text is literally the domain.
  • The Start hosting guide keeps its dashboard.render.com/select-repo blueprint link, since that's the real step-by-step walkthrough for creating a Blueprint, not a marketing CTA.

Happy to repoint any of those too if we'd rather every outbound Render link hit the landing page.

Verification

Single-file change; tsc and pnpm test pass (478 pass, 0 fail).

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Updates
    • Updated the “Deploy on Render” link to direct users to the TanStack page on Render.
    • Removed the previous blueprint repository-selection destination.

…page

Render built a co-branded landing page for TanStack at render.com/tanstack.
Repoint the partner-page conversion CTAs (previously the dashboard register
and blueprint deep-links) to it, keeping the existing UTM parameters. The two
URLs collapse to one constant since they now share a destination.

The "See compute pricing" deep-link and the footer render.com text-link are
left on their specific destinations, and the hosting-guide blueprint walkthrough
keeps its dashboard link, since those labels describe those exact pages.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Sep 18, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 01903578-1896-42e4-8833-790bb43be2d9

📥 Commits

Reviewing files that changed from the base of the PR and between b42cf50 and 4c524fc.

📒 Files selected for processing (1)
  • src/routes/partners.render.tsx

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.


📝 Walkthrough

Walkthrough

The Render partner route now points to https://render.com/tanstack. The deployment button uses the updated constant, and the separate blueprint URL constant was removed.

Changes

Render deployment link update

Layer / File(s) Summary
Update Render deployment destination
src/routes/partners.render.tsx
RENDER_HREF now points to the TanStack Render page. The Deploy on Render button uses this constant, and RENDER_BLUEPRINT_HREF was removed.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Feature

Suggested reviewers: tannerlinsley

Merge Risk: ⚪ Minimal · up to 4c524

The Render deployment CTAs now use the tracked TanStack landing page while specialized links remain unchanged, so the change is ready to merge.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: updating Render partner CTAs to use the Render/TanStack landing page.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
tanstack-com 4c524fc Commit Preview URL

Branch Preview URL
Sep 18 2026, 08:58 PM

@tannerlinsley
tannerlinsley merged commit e092142 into main Sep 20, 2026
7 checks passed
@tannerlinsley
tannerlinsley deleted the jonny/render-tanstack-landing branch September 20, 2026 06:23
tannerlinsley pushed a commit that referenced this pull request Sep 21, 2026
* feat(partners): route all Render referral surfaces to render.com/tanstack

Point every Render partner link across the site at the co-branded landing
page Render provided, keeping the existing UTM parameters (including the
per-placement utm_content). This covers the docs right-nav rail
(docs_rail/docs_strip), the partner grid, home grid, library grid, blog
rail, embed grid, and the partners directory — everything that resolves
through getPartnerHref or the partner record href.

The partner detail page CTAs already point here (#1281, merged).

Left intentionally unchanged, as these are functional or canonical rather
than referral links:
- canonicalHref (schema.org sameAs and the partners API websiteUrl) stays
  render.com, Render's canonical homepage
- the one-click "Deploy to Render" button (render.com/deploy?repo=…) keeps
  its repo param so it still deploys, matching the Netlify/Railway buttons
- the Start hosting guide's dashboard Blueprint walkthrough

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* feat(partners): point the last Render links at render.com/tanstack

Follow-up covering the three remaining Render URLs that were previously left
as functional/canonical, now repointed to the co-branded landing page per
request:

- canonicalHref -> render.com/tanstack (also drives the partner JSON-LD
  sameAs, the partners API websiteUrl, and the partner-page footer link;
  the "See compute pricing" deep-link still resolves to /pricing)
- the one-click "Deploy to Render" button (was render.com/deploy) now opens
  render.com/tanstack, keeping its repo and UTM params
- the Start hosting guide's "New > Blueprint" link (was the dashboard
  select-repo screen) now points at render.com/tanstack

Every Render link across the site now lands on render.com/tanstack.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants