docs: add FAQ #85
docs: add FAQ #85
Conversation
Refs #35 Adds answers to questions asked in that issue.
achingbrain
force-pushed
the
docs/add-faq
branch
from
a7f5b51 to
03223e8
Compare
There was a problem hiding this comment.
this a good start. I think there are other important questions though that we should answer like:
- why consider using Helia over js-ipfs
- why use Helia over the kubo-rpc-client
- what mechanisms does Helia have for content and peer routing?
- what data transports does Helia have
Basically I think we should extract out portions of https://blog.ipfs.tech/state-of-ipfs-in-js/ . Understood if that needs to happen in a followup.
| @@ -29,7 +29,7 @@ | |||
|
|
|||
| A lean, modular, and modern implementation of IPFS for the prolific JS and browser environments. | |||
|
|
|||
| See the [Manifesto](./MANIFESTO.md) and the [State of IPFS in JS blog post from October 2022](https://blog.ipfs.tech/state-of-ipfs-in-js/) for more info. | |||
| See the [Manifesto](./MANIFESTO.md), the [FAQ](./FAQ.md), and the [State of IPFS in JS blog post from October 2022](https://blog.ipfs.tech/state-of-ipfs-in-js/) for more info. | |||
There was a problem hiding this comment.
https://blog.ipfs.tech/state-of-ipfs-in-js/ was a snapshot in time. I think we should extract ou the parts that are relevant that are still true. We can point back to it as a historical pointer, but I think that should be a "Related / Historial Items" section likely in the manifesto doc. I think we want this repo to represent the latest state of affairs.
There was a problem hiding this comment.
Ok, maybe we can remove or update that in a different PR?
Co-authored-by: Steve Loeppky <[email protected]>
Refs #35