Jon-Kyle

Quick context on this! We needed a way to support a schema which [Catalog Works](http://catalog.works) uses. It’s based on zNFTs, and the contract address is the same as Zora. For...

awesome. so as you mentioned, enoki constructs it’s content object (with the`hypha` module) by traversing directories containing `index.txt` files. the directory name and it’s relation to the root directory becomes...

Was thinking in a channel. Down to do a PR for this btw!

Super solid stuff. Had thought about this and held off implementing as I’d like to retain feature parity between Node’s `fs` and the Dat `WebArchive` API exposed in [Beaker Browser](https://beakerbrowser.com/docs/apis/dat.html)....

You’re right! Field parsing and detecting the key/value needs to be improved, as there are several edge cases like this. Currently the array is created by splitting on `---`. Perhaps...

That’s pretty solid @jongacnik, hmm. Perhaps we could structure that simply by checking to see if there is a file appended with `filename-{INT}.jpg` the same way we check for metadata...

@s3ththompson nice, i’m thinking about this for the Enoki Panel too, but entirely clientside within the panel and using canvas to resize, get metadata, etc… @jongacnik could be cool to...

Btw this makes me want file data stored alongside pages as per https://github.com/jondashkyle/nanopage/issues/7 even more.

Btw this makes me want file data stored alongside pages as per https://github.com/jondashkyle/nanopage/issues/7 even more.

yeah, to do that in a unified way both client and server side requires a bit of thinking. seeing as hypha accepts `fs` as a param, we could simply see...