Rename enoki.json about enoki HOT 7 CLOSED

Yeah I agree, it fits in that conversation. We just need to keep gathering requirements and eventually the solutions should become obvious enough, I think

from enoki.

My only concern about site.json is that not all dat:// projects are Beaker based (sites) and in the future they might use this configuration too.

I know sites dominate and will dominate in the future too, but more Electron based apps or else may come.

from enoki.

I can't say for sure, but I agree I might consider a less generic name unless you're certain it's going to be a very reusable schema.

from enoki.

Two other ideas:

• Enoki is focusing on the dat:// ecosystem. Maybe this could be defined in dat.json?
• The site configuration could be a key in package.json, and we expect that to always be placed in the root directory of the archive, unlike now, which exists at /source/package.json

Zooming out a little further, @pfrazee, I wonder how we can configure applications in the dat:// ecosystem which share options, such as “Where does the content exist?”. There is already a bit of awkward overlap for this with Enoki. It stores the site title in a separate place than where the archive title is defined. This overlaps with the question of data portability, too.

from enoki.

@jondashkyle yeah I'm interested. I'm already thinking heavily about adding a generic links attribute to the dat.json, that will work like <link> elements (ie have href and rel and title). What all do you need to store?

from enoki.

@pfrazee The most important are title and content, with content being a path. Because dat.json. For an application like Enoki there are more granular settings which I wouldn’t think another application (even in the same space) would need access to.

The more I think about this, the more it seems to relate to the broader data portability project. Perhaps dat.json accepts a config key, which points to wherever your app configuration json is located, and it is formatted in json-lz, although that all seems pretty involved.

from enoki.

enoki.json is now site.json: #17

from enoki.