Summary

The repo docs now frame React on Rails as one product with an OSS starting point and a Pro upgrade path. The public site still does not make that transition especially explicit on the homepage/docs entry flow.

What I verified

Homepage

I checked https://reactonrails.com/ on March 26, 2026 UTC.

• The homepage has strong getting-started and migration CTAs
• It does not appear to surface an explicit OSS-vs-Pro comparison or feature-matrix style decision point
• It links to /docs/pro from the footer, but the homepage itself does not clearly explain when to stay OSS vs when to upgrade to Pro

Pro docs landing route

I checked https://reactonrails.com/docs/pro/.

• The route is live (200)
• It is still rendering the legacy pro/react-on-rails-pro content shape
• The page still includes old support-plan / email-first wording and does not present the concise modern upgrade story as clearly as the repo docs now do

Why this matters

• New users should encounter one product story: start with OSS, upgrade to Pro when you need RSC, streaming SSR, or higher SSR throughput
• The current site makes the docs more modern than the public marketing/docs entry flow
• This is the public-facing counterpart to the repo-side docs cleanup work

Related issues

• Related to shakacode/react_on_rails#2838 for the stale react-on-rails-pro.md source page and references
• Related to Fix dead pro.reactonrails.com destination #59 for the dead pro.reactonrails.com destination
• Different from Rewrite sidebars.ts with explicit ordering and Pro interleaving #47, which was about sidebar ordering/interleaving
• Different from Add redirects for legacy /docs/guides/* documentation routes #63, which is about legacy docs redirects

Acceptance criteria

• Homepage or top-level docs landing makes the OSS-to-Pro upgrade path explicit
• Public site includes a clear comparison or decision point for OSS vs Pro
• /docs/pro/ presents the modern Pro story clearly: evaluation policy, who should upgrade, and the short upgrade path
• Public-site CTAs and docs navigation align with the canonical /docs/pro destination