Follow-up: Align site-owned create-app and examples copy with Pro-first docs

[justin808]

Summary

React on Rails PR #4217 changes the new-app story: npx create-react-on-rails-app my-app should now be presented as the Pro/RSC default path for React 19.2 support, with --standard as the explicit OSS-only escape hatch. The docs pages under /docs/... are sourced from shakacode/react_on_rails and should update through the existing docs-updated dispatch after that PR merges.

This issue tracks the site-owned Docusaurus pages that are not generated from the monorepo docs.

Suggested work

• Update prototypes/docusaurus/src/constants/prompts.ts so the homepage Start a new app prompt says the default generated app is the Pro/RSC React 19.2 path, and mentions --standard only as the OSS-only escape hatch if the prompt needs that caveat.
• Review /examples copy in prototypes/docusaurus/src/pages/examples.tsx and demo metadata in prototypes/docusaurus/src/constants/demos.ts for consistency with the Pro-first examples direction.
• Coordinate with Add flagship OSS React on Rails demo to examples #129 before adding or describing the Flagship demo: do not position it as the OSS baseline unless that is still intentionally true. The React on Rails docs now treat Flagship as a product-style baseline / possible Pro-transition reference that should be checked against its README before public stack claims.
• After PR #4217 lands and docs sync, verify the live /docs/getting-started/create-react-on-rails-app, /docs/getting-started/quick-start, and /examples pages tell one coherent new-user story.

Source

• React on Rails PR: Make Pro the default create-app path react_on_rails#4217
• Related site issue: Add flagship OSS React on Rails demo to examples #129

Non-goal

Do not edit generated docs directly under content/upstream/docs or prototypes/docusaurus/docs; those come from the React on Rails monorepo sync.

[justin808]

Blocked audit for this batch (checked 2026-06-26T08:39:54Z): this site follow-up should not be implemented yet because upstream react_on_rails#4217 is still OPEN and unmerged.

Current upstream state from GitHub metadata:

• PR: Make Pro the default create-app path react_on_rails#4217
• State: OPEN
• Draft: false
• Head SHA: 8379fe5dd098a3200ce69e7643f7c0af2bffcd79
• Merge state: CLEAN
• Merged at: null
• Fetched check rollup: 52 checks, 0 failing, 0 pending

No reactonrails.com code change or PR was opened from this issue in this pass. Next action: resume this issue after upstream #4217 merges and after the site batch dependencies (#130 and #131) have landed, then sync/update the generated/source docs flow rather than hand-editing generated output.

[justin808]

Codex update: upstream source PR shakacode/react_on_rails#4232 is open on head cb594c28. Current-head required gate, Claude, CodeRabbit, and all hosted checks except Rspec test for gem / rspec-package-tests (4.0, latest, generators) are passing. That remaining generator shard has been in Run rspec tests since 2026-06-27 06:08 UTC; GitHub does not expose logs until completion. I am holding the reactonrails.com generated prompt PR and merge until upstream CI clears so the site artifacts stay delegated to the canonical upstream prompt source. Local site validation against the regenerated artifacts passes: npm run test:prepare-prompts and npm run build.

[justin808]

Codex update: upstream source PR shakacode/react_on_rails#4232 is now on head 7e6b4dde. Current-head required gate, Claude, CodeRabbit, and all hosted checks except Rspec test for gem / rspec-package-tests (4.0, latest, generators) are passing or skipped. That remaining generator shard has been in Run rspec tests since 2026-06-27 06:50 UTC; GitHub does not expose logs until completion. I am still holding the reactonrails.com generated prompt PR and merge until upstream CI clears so the site artifacts remain delegated to the canonical upstream prompt source. Local site validation against the regenerated artifacts passes: npm run test:prepare-prompts and npm run build.