# IPFS Ecosystem/DEV REL needs ###### tags: `team` ### Awesome-ipfs - https://github.com/ipfs/awesome-ipfs - needs to be updated/purged of dead links/projects - add new projects ### ipfs toolbox - devtools enabled addon - https://hackmd.io/sJZib5iiShGxmQ2x-OD8SQ ### deploy to ipfs Developers, in the web2 world, have a slew of options on how to deploy their creation on the web and manage that. IPFS doesn't "really" seem to have that yet. There are Github Actions with IPFS support that can bring you somewhere. But there aren't ironed out usecases and guidelines that help you in deploying a website on the IPFS network straight from your development environment like you do have that tooling for web2. This might be the devops category. ### persistent misconception about `ipfs add` There's a lot of blog posts out there that describe how to make something available on IPFS. Many of those same posts either assume your data will always be there (which it won't) or they don't mention it at all. There definitely are blog posts out there doing a great job explaining it! The issue however is that the "common" assumption - just look at ipfs-chatter on discord - is that adding a file to IPFS makes it available on the network forever. That's a misconception that can be tackled by just writing more about IPFS with accurate information. For example having such articles be part of the IPFS blog would make it easy to find and point to as "the right source".