You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why features are not right after the name and description?
From perspective of viewer I want to know what it is first and then how to use or contribute.
So features it the key factors which will determine my decision on should I use this library.
The text was updated successfully, but these errors were encountered:
Is there some specific project/example where it makes more sense to have features first?
Why it's like this now: I think the first paragraph should be the sales pitch and as a developer I think the next important thing is to try it out myself. IIRC this structure originally came from researching a lot of readmes and trying to pick the best structure 🙂
From my perspective features sells first. Why I as the developer should try this repo. What special it can give to me and what differentiate this project from others.
Why features are not right after the name and description?
From perspective of viewer I want to know what it is first and then how to use or contribute.
So features it the key factors which will determine my decision on should I use this library.
The text was updated successfully, but these errors were encountered: