-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Awesome API Documentation Endeavour #615
Comments
Thanks @dignifiedquire! I would love to help out with either js-ipfs-api or js-ipfs! 🤗 Also, I can probably tackle js-multiaddr |
|
@dignifiedquire we should probably add a link to the repository in the top right or something like that in the theme as well |
Yes, but need to implement that first in documentation.js, ref documentationjs/documentation#612 |
@victorbjelkholm I take that back, added it :) |
@victorbjelkholm @diasdavid just created ipfs/aegir#78 |
Additional todos for (not needed for initial release though)
|
@dignifiedquire this is shaping to be awesome! ❤️ I believe to make this a perfect landing, we just need to make sure that a) feedback is requested, b) feedback is collected. Let's focus on getting js-ipfs and js-ipfs-api done first as those will be the most used doc pages. |
I would very much like this. I'm not too happy with the API section just being a link to somewhere off-site; that means that the documentation is not close to the code. @dignifiedquire Can I help with this? Is there a ticket tracking this, elsewhere? |
the documentation is right in the code, so it's even closer now :P |
@dignifiedquire I believe that is not a valid answer. Can you provide @RichardLitt with:
|
I'm sorry I just don't agree with the notion of stuffing the readme full of api documentation if we don't have to. Especially for projects where the documentation is more than just a couple of methods. Putting it in a separate markdown file which is not tracked in git and published to npm I think makes sense though.
|
Fair.
Why no git track? |
Because it's auto generated and the risk of things getting out of sync on a per commit basis is very high. |
This references the Awesome Documentation effort. See ipfs/js-ipfs#615
This references the Awesome Documentation effort. See ipfs/js-ipfs#615
For awesome documentation, each example link should be pinned somewhere so that the reader can try the example. E.g. the example for "This is some data" on the examples page doesn't resolve: Also, the links for the example web site on this page don't work: |
Moved the entire tracking of this awesome endeavour to its own PR - #651 |
We want to improve the documentation in the whole project and for that this endeavour exists.
To improve the documentation we settled on using
jsdoc
style inline comments to describe the APIs and after that using documentation.js to generate beautiful docs.If you want to help out, please comment on this issue which module you are tackling.
Test Instructions
Currently the integration intoaegir
is not yet done, so when documenting you can usedocumentation.js
directly to test that everything works fine.^9.2.0
"docs": "aegir-docs"
npm run docs
docs/index.html
in your favorite browserModules
IPFS
IPLD
libp2p
multiformats
Other work
The text was updated successfully, but these errors were encountered: