docs(ensnode.io): emotional red/green narrative framing in Why ENSNode pages#2253
Conversation
…e pages Apply caution-frame (red :::danger) / solution-frame (green :::tip) panels with nested LinkCards across the high-visibility Why ENSNode pages, per docs feedback. Pairs with the card-in-aside styling from PR #2233. - keep-ens-working: red panel above the fold linking to Key Limitations; Next Steps split into a red (problem) and green (solution) panel. - why-ensnode index: lead with the stakes (red panel), then the solution (green panel), then a single "How ENSNode delivers" proof cluster that folds in the former One unified API / Multichain / Full-stack sections (removing the awkward standalone "Multichain by default" heading). - ensv2-readiness: "Be ready!" panel blue -> green + Omnigraph card; Key Limitations wrapped in a red panel.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Warning Review limit reached
More reviews will be available in 21 minutes and 56 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: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThree documentation pages restructured to clarify ENSv2 compatibility messaging and promote the ENS Omnigraph API: ENSv2 readiness page reorganized with new callouts and link cards, Why ENSNode index page segmented to separate subgraph incompatibility from Omnigraph value proposition, and Keep ENS Working page updated with breaking-change warnings and migration call-to-action. ChangesENSv2 Readiness and Omnigraph Messaging
🎯 2 (Simple) | ⏱️ ~12 minutes Possibly Related PRs
Suggested Labels
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Pull request overview
This PR updates the high-visibility “Why ENSNode” documentation pages to use a clearer problem/solution narrative, framing ENS Subgraph risks in red danger panels and ENSNode’s Omnigraph path forward in green tip panels, with LinkCards embedded for quick navigation.
Changes:
- Adds above-the-fold red
dangerframing and splits “Next Steps” into problem (red) vs solution (green) on Keep ENS apps working. - Reworks the Why ENSNode index to lead with stakes (red), then solution (green), and consolidates value props into a single “How ENSNode delivers” section.
- Updates ENSv2 Readiness to use a green
tip“Be ready!” panel with an Omnigraph LinkCard and wraps Subgraph limitations in a reddangerpanel.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/ensnode.io/src/content/docs/docs/integrate/why-ensnode/keep-ens-working.mdx | Adds red “risk” framing above the fold and splits Next Steps into red problem vs green solution panels with LinkCards. |
| docs/ensnode.io/src/content/docs/docs/integrate/why-ensnode/index.mdx | Reorders and consolidates the page narrative into stakes → solution → proof points, updating headings and LinkCard placement. |
| docs/ensnode.io/src/content/docs/docs/integrate/why-ensnode/ensv2-readiness.mdx | Switches the lead Aside to tip, adds an Omnigraph LinkCard, and wraps Key Limitations in a danger Aside. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/ensnode.io/src/content/docs/docs/integrate/why-ensnode/index.mdx`:
- Around line 14-27: The LinkCard instances for "Key Limitations of the ENS
Subgraph" are inconsistent; standardize all occurrences by using a single
canonical title and description (update the LinkCard props in every place where
LinkCard is used for this destination). Locate each LinkCard with
title/description props referencing "Subgraph" (the LinkCard component) and
replace their title with "Key Limitations of the ENS Subgraph 🚨" and
description with "The full list of ways the ENS Subgraph falls short today — and
why each one breaks with ENSv2." so all four instances use the exact same text.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: f98f8b5c-a10b-4e26-b307-1b51d408df38
📒 Files selected for processing (3)
docs/ensnode.io/src/content/docs/docs/integrate/why-ensnode/ensv2-readiness.mdxdocs/ensnode.io/src/content/docs/docs/integrate/why-ensnode/index.mdxdocs/ensnode.io/src/content/docs/docs/integrate/why-ensnode/keep-ens-working.mdx
Greptile SummaryThis PR applies emotional red/green narrative framing to three high-visibility "Why ENSNode" documentation pages, wrapping problem-oriented content in
Confidence Score: 5/5Documentation-only content restructuring with no logic, config, or code changes — safe to merge. All three files contain only MDX prose and Starlight component markup. No broken link targets, no missing imports, and every component was already imported before this PR. The aside-syntax mix and duplicate Key Limitations cards were already acknowledged as intentional in prior review threads. No files require special attention. Important Files Changed
Reviews (3): Last reviewed commit: "docs: standardize Key Limitations card t..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@greptile review |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Apply caution-frame (red
:::danger) / solution-frame (green:::tip) panels with nested LinkCards across the high-visibility Why ENSNode pages, per docs feedback. Pairs with the card-in-aside styling from #2233.Changes