What type of issue is this?

Other

What information was incorrect, unhelpful, or incomplete?

This came up in Slack by @chrisdavidmills while looking into documenting https://w3c.github.io/payment-method-manifest/ which is a new manifest file.

Currently, we document the App manifest features in the html.manifest.* tree. Given it is not the "HTML manifest" and that there is now another manifest file, it might make sense to introduce a top-level manifests/ folder.

A new top-level manifests folder with two sub folders:

• manifests/app/*.json for https://w3c.github.io/manifest/ and friends.
• manifests/payment-method/*.json for https://w3c.github.io/payment-method-manifest/

And exports like so:

• manifests.app.share_target
• manifests.payment-method.default_applications

This will be expandable if new manifest files are invented.

MDN documents the App manifest under https://developer.mozilla.org/en-US/docs/Web/Manifest right now. If we choose to update the BCD structures, BCD queries on MDN will need updating and maybe some thoughts are needed to take into account that there can be several kinds of manifest files.

Thoughts?

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

No response

Did you test this? If so, how?

No response

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response