Add the OSS flagship demo to examples#130
Conversation
Greptile SummaryThis PR adds the OSS flagship React on Rails demo to the shared demo catalog, inserting it as the first entry in
Confidence Score: 3/5The catalog entry and asset are correct, but the OSS demo will be rendered under a section explicitly labeled "Pro… and RSC" on the live /examples page. The new OSS flagship demo is placed in category: 'flagship', whose section heading in examples.tsx reads "Production-style apps on React on Rails Pro, React 19, and RSC." The demo's own tagline says the opposite — "no Pro or RSC required." Any visitor to /examples sees the OSS demo listed under a heading that misrepresents it as a Pro/RSC app, which is a live content accuracy problem on the deployed site. prototypes/docusaurus/src/pages/examples.tsx — the 'flagship' group heading needs updating to cover both OSS and Pro demos, or the new OSS entry needs a distinct category. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["demos.ts\n(catalog source of truth)"] -->|"filter by category"| B["examples.tsx\ndemoGroups loop"]
B --> C["'flagship' group\nheading: 'Pro, React 19, and RSC'"]
B --> D["'starter' group"]
B --> E["'legacy' group"]
C --> F["OSS flagship demo\n⚠️ tagline: 'no Pro or RSC'"]
C --> G["marketplace\n(Pro + RSC)"]
C --> H["hacker-news\n(Pro + RSC)"]
C --> I["octochangelog\n(Pro + RSC)"]
C --> J["gumroad\n(Pro + RSC)"]
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
A["demos.ts\n(catalog source of truth)"] -->|"filter by category"| B["examples.tsx\ndemoGroups loop"]
B --> C["'flagship' group\nheading: 'Pro, React 19, and RSC'"]
B --> D["'starter' group"]
B --> E["'legacy' group"]
C --> F["OSS flagship demo\n⚠️ tagline: 'no Pro or RSC'"]
C --> G["marketplace\n(Pro + RSC)"]
C --> H["hacker-news\n(Pro + RSC)"]
C --> I["octochangelog\n(Pro + RSC)"]
C --> J["gumroad\n(Pro + RSC)"]
Reviews (1): Last reviewed commit: "Show the OSS flagship demo in examples" | Re-trigger Greptile |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c706782abe
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| repoUrl: 'https://github.com/shakacode/react-on-rails-demo-flagship', | ||
| demoUrl: 'https://flagship.reactonrails.com', | ||
| image: '/img/demos/flagship.webp', | ||
| category: 'flagship', |
There was a problem hiding this comment.
With category: 'flagship', this new card is rendered on /examples under the existing flagship heading Production-style apps on React on Rails Pro, React 19, and RSC. in prototypes/docusaurus/src/pages/examples.tsx lines 17-19. The new tagline explicitly says the app requires no Pro or RSC, so visitors now see an OSS-only demo presented as part of the Pro/RSC section; adjust the group heading/category or add a separate OSS group.
Useful? React with 👍 / 👎.
|
Cloudflare preview deployed.
|
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_48cea633-c242-4e3c-ab98-ad3054f17150) |
WalkthroughA new ChangesFlagship Demo Catalog Entry
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
|
Addressed the Greptile content-accuracy finding in d16a446: the Local checks after the change: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_8555d732-df77-4787-84d5-1db38ac0a44e) |
1 participant
Summary
/examples.https://flagship.reactonrails.com.Closes #129.
Refs #113.
Thumbnail Audit
main, and touches examples plus scripts; this PR starts fromorigin/mainand does not depend on or copy that stale branch.flagship,marketplace,tanstack-starter,legacy-tutorial,hacker-news,octochangelog, andgumroad.flagship.webpasset is 1280x720 and references/img/demos/flagship.webpfrom the catalog.Tests
git diff --checknpm run build(passes; existing Docusaurus broken-link/anchor warnings are still reported by the site build)Coordination / Workflow Notes
UNKNOWN;.agents/skills/pr-batch/SKILL.mdand.agents/workflows/pr-processing.mdare absent both locally and onorigin/main, so this used the installed$pr-batchfallback workflow.agent-coord status:UNKNOWN; bounded status timed out for the worker lane, so no reliable live backend status was available.codex-examples-129-113for Add flagship OSS React on Rails demo to examples #129/Add real screenshots/thumbnails for demo apps (homepage + /examples) #113. Worker was stopped before PR creation after shared-workspace overlap was detected; coordinator split the path-scoped changes and opened this PR.Codex Decision Log
mainalready includes the flagship asset.Note
Low Risk
Documentation and marketing catalog changes only; no runtime or application logic.
Overview
Adds the OSS flagship demo (
react-on-rails-demo-flagship/flagship.reactonrails.com) as the first entry in the shareddemoscatalog, withfeatured: trueand thumbnail/img/demos/flagship.webp, so it appears in homepage Live demos and under Flagship demos on/examples. The tagline positions it as the OSS baseline (Rails 8.1, React 19, SSR, Redux, Shakapacker) without Pro or RSC.Updates the flagship section heading on
/examplesfrom Pro/RSC-only wording to “Full-stack apps from the OSS baseline to React on Rails Pro, React 19, and RSC.”Reviewed by Cursor Bugbot for commit d16a446. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
New Features
Documentation