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

Add README for the docs folder. #5049

Closed
schomatis opened this issue May 30, 2018 · 4 comments
Closed

Add README for the docs folder. #5049

schomatis opened this issue May 30, 2018 · 4 comments
Assignees
Labels
topic/docs-ipfs Topic docs-ipfs

Comments

@schomatis
Copy link
Contributor

And maybe also include the table of contents in the repo README to make them more visible and accessible to the user.

@schomatis schomatis added the topic/docs-ipfs Topic docs-ipfs label May 30, 2018
@schomatis schomatis self-assigned this May 30, 2018
@schomatis schomatis added this to the Files API Documentation milestone May 30, 2018
@whyrusleeping
Copy link
Member

Sounds good to me!

@Mr0grog
Copy link
Contributor

Mr0grog commented Jun 2, 2018

I tried to effectively do this in ipfs-inactive/docs#68 here: https://ipfs.io/ipfs/QmVUdHfpo9hyC8wXmgd2frRrsp83iRvuL8HWyp1LPzjsPq/reference/go/overview/

It doesn’t cover a few files (like AUTHORS and generate-authors.sh) that didn’t seem to fit in the docs site. I’m struggling a little with thinking of a good way to have a README here while also exposing a useful list of docs in the docs site and not making extra work for people (the examples directory in js-ipfs poses a similar issue).

@schomatis
Copy link
Contributor Author

As a temporary measure maybe we could add a placeholder REAMDE that just links to https://ipfs.io/ipfs/QmVUdHfpo9hyC8wXmgd2frRrsp83iRvuL8HWyp1LPzjsPq/reference/go/overview/.

@Mr0grog
Copy link
Contributor

Mr0grog commented Jun 7, 2018

OK, the more I think about this, the more I feel like we should just put a copy of that page as the README in the docs folder.

  • Linking from here to the docs site and then back to the docs folder seems like some unnecessary jumping around.

  • We’ll probably move some docs move from here to the docs site, at which point what’s relevant for pages in the docs site to cover and what’s relevant for a README here to cover will diverge.

  • I think I’m more worried than is really reasonable about the duplication :)

I’ll go ahead and make a PR for this now.

Mr0grog added a commit to Mr0grog/go-ipfs that referenced this issue Jun 7, 2018
Also adds a link to the authors list in the top-level README.

License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
Mr0grog added a commit to Mr0grog/go-ipfs that referenced this issue Jun 7, 2018
Also adds a link to the authors list in the top-level README.

License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
Mr0grog added a commit to Mr0grog/go-ipfs that referenced this issue Jun 7, 2018
Also adds a link to the authors list in the top-level README.

License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
djdv pushed a commit that referenced this issue Jun 27, 2018
Also adds a link to the authors list in the top-level README.

License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic/docs-ipfs Topic docs-ipfs
Projects
None yet
Development

No branches or pull requests

3 participants