Tighten the README and cut marketing filler - #346
Conversation
Rewrite the top-of-file copy: a one-line tagline, the intro folded into two
short paragraphs, and the Highlights bullet list dropped. Trim the benchmark,
Reflex, and how-it-works sections, remove the "What you can build today"
section that restated Highlights, and rename the example-gallery labels to
what each chart actually is ("cosmic observatory" -> "HR diagram").
Also move Examples above How it works, drop the Documentation section,
replace the em dashes in the roadmap list with colons, and point the styling
guide and capability matrix at absolute GitHub URLs so they resolve on PyPI.
Prose drops from 1145 to 761 words. No code samples, images, or benchmark
numbers change.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughREADME content is condensed and reorganized across onboarding, customization, Reflex integration, examples, architecture, and roadmap sections. No exported or public declarations are changed. ChangesREADME Documentation Refresh
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Drop the centered bold wrapper so the first sentence is left-aligned prose like the rest of the README.
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 `@README.md`:
- Around line 115-116: Update the README references covered by this change,
including the compatibility guide, example guide, gallery images, and notebooks,
to use absolute GitHub repository URLs instead of relative paths so they resolve
correctly outside GitHub.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| See the [compatibility guide](spec/matplotlib/compat.md); not all charts and | ||
| functionality are supported yet. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Make changed repository links portable outside GitHub.
The compatibility guide, example guide, gallery images, and notebooks still use relative paths. If this README is rendered on PyPI, these links/assets may resolve against pypi.org and break. Convert the changed repository references to absolute GitHub URLs, or verify PyPI rendering before merge.
This follows the PR objective that PyPI-relative links and image URLs remain follow-up items.
Also applies to: 219-226
🤖 Prompt for 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.
In `@README.md` around lines 115 - 116, Update the README references covered by
this change, including the compatibility guide, example guide, gallery images,
and notebooks, to use absolute GitHub repository URLs instead of relative paths
so they resolve correctly outside GitHub.
Merging this PR will not alter performance
Comparing Footnotes
|
Makes the README read less like generated copy and about a third shorter. Prose goes from 1145 to 761 words; no code samples, images, or benchmark numbers change.
Copy
What you can build today(restated Highlights) andDocumentation.Structure
Is XY right for me?→ Installation → Getting started → Customize every layer → Benchmarks → Reflex → Examples → How it works → Roadmap. Examples moved above How it works.Follow-ups, not in this PR
pyproject.tomlsetsreadme = "README.md", so this file is the PyPI long description, where relative links 404. The styling guide and capability matrix now use absolute GitHub URLs; 20 other links and all 4 images still don't. Images needraw.githubusercontent.comto render there.spec/api/api-examples.mdandCHANGELOG.mdlost their only link when the Documentation section went. Worth re-homing if they should stay discoverable.16–18×in Benchmarks keeps an en dash as a numeric range.Summary by CodeRabbit