docs: add a "Why react-call?" section to the README#117
Open
alfredmouelle wants to merge 1 commit into
Open
Conversation
|
@alfredmouelle is attempting to deploy a commit to the desko27's projects Team on Vercel. A member of the Team first needs to authorize it. |
alfredmouelle
marked this pull request as ready for review
July 16, 2026 21:13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #107.
What
Why react-call?section just before Getting started./whyadded to the header links and the Contents list.Why
The thread on #107 has the diagnosis in it. @fikrikarim asked for the comparison, @waken22 pointed at the
/whypage, and the reply was "I didn't see that. I only read the repo."The README never links to
/why, not once in 545 lines. The page is orphaned from the repo, so the argument only reaches people who already found the site. It is also absent from the npm page, which is where a lot of first contact happens.So this does both halves: the section itself, and the link, so the page stops being invisible from here.
Approach
Condensed, not rewritten. The prose is your
/whypage tightened up, the two code samples are copied verbatim, and I have not invented any new arguments. It closes with a note pointing at/whyfor the full version.The code samples are stacked vertically rather than side by side: a two column table with fenced code renders reliably on GitHub but not on npm, and npm is exactly the surface where this content is missing.
Scoped to the README. Your other point about improving the
/whysection itself is its own PR, happy to take that afterwards if you still want it.No changeset: docs only, nothing published changes.