While helping out with HackFS, several questions came up that I think would make great tiny examples.

tiny examples that I think would be useful for the community

based on some recent ETHGlobal HackFS questions in the #partner-ipfs channel.

• Upload file(s)/folder(s), then create a car file
• How to do content-type detection of bytes received (there are many ways, but showing one and linking to discussions would be useful I think)
• Video streaming -> helia blockstore (writing streaming video)
• Helia blockstore -> video streaming (reading bytes as streaming video)
• Rendering different (potentially unknown) content; Similar to https://github.com/ipfs-shipyard/helia-service-worker-gateway/blob/main/src/components/CidRenderer.tsx
• Getting files/content/etc into a format ready for making deals similar to https://data.lighthouse.storage/

Some thoughts about how we should add tiny examples in this repo:

catch-all with links to Codepen/stackblitz

I don't think it would make sense to use codepen/stackblitz for these because they would quickly become out of date or forgotten.

Single repo for each tiny example

A lot of overhead and a lot of duplicated code.

Single repo for all tiny examples

I think this option is best.

We could create a single repo, similar to helia-101, where we share the main helia instance, and only render different UI components via SPA, where each path is its own codepen-esque view for a particular use-case.

Questions for @Helia-Dev (@achingbrain & @whizzzkid) and @discordian folks:

1. Does this seem valuable to you?
2. Would you rather have a single example for these smaller scenarios, or should we have each as its own separate example repo?
3. Is there a better option I didn't consider?
4. Are there other tiny examples that may make sense?