Add HiChee.com to examples#119
Conversation
|
Warning Review limit reached
More reviews will be available in 57 minutes and 7 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 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 |
Greptile SummaryThis PR adds a "Production sites" section to the Examples page, listing HiChee.com as a live React on Rails deployment with a "Visit site" link and no implied source-code access. Hero copy is updated to reflect that the page covers live products alongside demos and starters.
Confidence Score: 4/5Documentation-only change with no application logic, auth, or data handling; safe to merge with minor polish considerations. The change is confined to a static marketing page — new CSS classes are well-scoped, custom properties are defined for both themes, and the external link is handled correctly by the Docusaurus Link component. Two small rough edges exist: the Production sites section header renders unconditionally (inconsistent with the guarded demo-group pattern), and the link text Visit site is ambiguous for screen readers if the list grows. No files require special attention; both findings are in examples.tsx and are easily addressable before or after merge. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[ExamplesPage] --> B[Hero Section]
A --> C{productionSites.length > 0?}
C -->|currently always true| D[Production Sites Section]
C -->|if empty - no guard| D
D --> E[siteCard per entry - HiChee.com]
E --> F[Link href=https://hichee.com/ - Visit site]
A --> G[demoGroups.map]
G --> H{groupDemos.length === 0?}
H -->|true| I[return null]
H -->|false| J[Section with DemoCards]
Reviews (1): Last reviewed commit: "Merge main into HiChee examples branch" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| <Link className={styles.siteLink} href={site.href}> | ||
| Visit site | ||
| </Link> |
There was a problem hiding this comment.
| <Link className={styles.siteLink} href={site.href}> | |
| Visit site | |
| </Link> | |
| <Link className={styles.siteLink} href={site.href}> | |
| Visit {site.title} | |
| </Link> |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| <section className="container"> | ||
| <div className={styles.sectionHeader}> | ||
| <p className={styles.sectionEyebrow}>Production sites</p> | ||
| <h2>Live products built with React on Rails.</h2> | ||
| </div> | ||
| <div className={styles.siteGrid}> | ||
| {productionSites.map((site) => ( |
There was a problem hiding this comment.
productionSites is later emptied during development or content changes. The existing demo-group pattern guards against this with an early return null. Adding the same guard keeps the behaviour consistent and avoids a dangling section title with no cards.
| <section className="container"> | |
| <div className={styles.sectionHeader}> | |
| <p className={styles.sectionEyebrow}>Production sites</p> | |
| <h2>Live products built with React on Rails.</h2> | |
| </div> | |
| <div className={styles.siteGrid}> | |
| {productionSites.map((site) => ( | |
| {productionSites.length > 0 && ( | |
| <section className="container"> | |
| <div className={styles.sectionHeader}> | |
| <p className={styles.sectionEyebrow}>Production sites</p> | |
| <h2>Live products built with React on Rails.</h2> | |
| </div> | |
| <div className={styles.siteGrid}> | |
| {productionSites.map((site) => ( |
|
Cloudflare preview deployed.
|
1 participant
Summary
Test plan
npm --prefix prototypes/docusaurus run typechecknpm run buildBuild passes; it still emits the existing Docusaurus broken-link and broken-anchor warnings unrelated to this change.
Note
Low Risk
Documentation/marketing UI only; no auth, data, or application logic changes.
Overview
The Examples page now highlights production deployments alongside demos and starters, not only source-backed examples.
A new Production sites block appears above the existing demo groups. It lists HiChee.com with a short product description and a Visit site link (no repo link). Hero kicker, title, and lead copy were updated to mention live products and production references.
Styling adds a single-column site card layout (
siteGrid,siteCard,siteLink) separate from the three-column demo grid.Reviewed by Cursor Bugbot for commit cf53c5d. Bugbot is set up for automated code reviews on this repo. Configure here.