-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Cleaning up main REAMDE #5087
Comments
/cc @Mr0grog |
Hmmmmm! Initial reactions:
I think installation instructions are really important, so I’m wary of hiding them. But you are totally right that this section is way too big and long, with a huge number of choices and options. My take:
I think “usage” sections are also super important in the README, but they should be more like what the “getting started” section is. You’re right that just printing the output of My take: replace the existing “usage” section with the content of the “getting started” section. Maybe add some more stuff there (or, I guess, to “some things to try”).
100% agree! Just move the docker stuff into a separate doc and link it (maybe from the “install” section) 👍 👍 👍 |
Also, a thing that is missing from usage/getting started: clearly stating that normal usage is to run |
Cleaning this up would help making excellent documents like #5864 more visible. |
I would like to give more visibility to sections like "Getting Started", "Contributing" and "Want to read our code?". Maybe we could:
Move the Install section (with many OS/architecture specific details) to its own document in the
docs
dir and just link to it in the README.Remove the Usage which takes up a lot of space and just shows a (possible outdated) help message that the user can easily obtain by typing the
ipfs
command (which can be hinted in the "Getting Started" section). At the very least it can be moved to its owndocs
entry.Maybe reduce the Docker usage section in favor of enlarging the simpler and more accessible to the user (who may not know how to use Docker) Some things to try section.
The text was updated successfully, but these errors were encountered: