Throwing IPFS and libp2p in the same basket is a mistake I think. I was hesitant too, but it’s quite developed. Libp2p documentation is decent, especially with AI to help. Try this link, it helped us at the start. https://proto.school/introduction-to-libp2p/

We don’t use a lot of the things in libp2p, but having multiplexing & QUIC with no certificate authorities is quite nice. I think it’s wise to pick out the pieces that work and leave the junk behind. 

 By that I mean IPFS is an over-complicated mess and overly relies on P2P tactics for data storage/serving… user-server model of nostr is key.

Although, libp2p standalone without IPFS is quite nice. Just like how Merkle Trees without IPFS is nice. Took the good pieces. 🧩