shakacode / shakacode/reactonrails.com

Add flagship OSS React on Rails demo to examples

Open
#129 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation enhancement
Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Summary

Add the new OSS flagship React on Rails demo to the examples catalog and docs. This is the finished example counterpart for the clone-and-run React on Rails baseline: Rails 8.1, React 19, Redux Toolkit, Shakapacker/Rspack, SSR, ActiveRecord CRUD, SQLite, no Pro/RSC/license requirements.

Repo: https://github.com/shakacode/react-on-rails-demo-flagship
Current staging URL: https://rails-9mtcnca82xcvj.cpln.app
Proposed canonical URL: https://flagship.reactonrails.com

Suggested work

  • Add an examples/catalog entry for the flagship OSS demo.
  • Link to the GitHub repo and live demo.
  • Add a screenshot/thumbnail for the example card.
  • Mention that this is the OSS baseline demo, not Pro and not RSC.
  • Configure flagship.reactonrails.com as the canonical public URL if we want a stable marketing/docs link.
  • Update the demo repo README live-demo link once the canonical subdomain is active.
  • Verify the live demo with the repo smoke check after DNS/custom-domain setup.

Notes

The staging deployment has already passed SSR smoke against the current endpoint: the server-rendered HTML contains 6 seeded task cards and the marker Render the first screen on the server</h3>.

The custom subdomain is preferable before adding the demo prominently to reactonrails.com, so the docs do not point at a generated cpln.app hostname.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the examples catalog and the documentation page where demo cards are defined, then review the flagship repository README and its repo smoke check. Add the OSS demo entry, repository and live links, screenshot, and clear non-Pro/non-RSC labeling; if the canonical subdomain is configured, update the README and verify the live SSR response and seeded task cards.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, rails, react, redux, sqlite
Domain
devops, documentation, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
54/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.