Consider a new name

“custom-elements.json” is a filename and not necessarily a description of the file’s contents or purpose. The file specific name also might not be required to be custom-elements.json. On npm it could be referenced from a package.json field, like the "types" field. In other systems, like databases, the name might not matter or even exist.

A few options to consider:

• Custom elements manifest
• Custom elements docs file
• Package docs file

Considering that the format will be capable of pretty fully describing package contents, being a “package docs file” might make sense. There very well might be other communities interested in shared docs infrastructure, even if that isn’t a primary goal right now.

[justinfagnani]

I like the name “Custom Elements Manifest”. The filename would presumably still usually be custom-elements.json though we should also standardize a package.json field to point to the manifest so that indexers can see that a package has a manifest without having to unpack the entire tarfile.

[justinfagnani]

Sounds like consensus to me 😃