Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Features to the top #18

Open
Masyaka opened this issue Mar 8, 2023 · 2 comments
Open

Features to the top #18

Masyaka opened this issue Mar 8, 2023 · 2 comments

Comments

@Masyaka
Copy link

Masyaka commented Mar 8, 2023

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.

@jehna
Copy link
Owner

jehna commented Mar 8, 2023

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 🙂

@Masyaka
Copy link
Author

Masyaka commented Apr 17, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants