See discussion here in the context of ember addons, here in bsky in the context of eslint rules, and an example ecosystem-only-registry here in the context of vite plugins.
The idea is for Packages to say that they are part of an Ecosystem. This would allow us to filter packages, show badges, show structured info cards about them, etc.
In ember, the package will have a field in its package.json stating that it is an ember addon. If we end up defining a record for a package (in the project PDS? or as part of a proxy website sitting before centralized platforms like nmpjs.com?), then this info could be there instead.
See discussion here in the context of ember addons, here in bsky in the context of eslint rules, and an example ecosystem-only-registry here in the context of vite plugins.
The idea is for Packages to say that they are part of an Ecosystem. This would allow us to filter packages, show badges, show structured info cards about them, etc.
In ember, the package will have a field in its package.json stating that it is an ember addon. If we end up defining a record for a package (in the project PDS? or as part of a proxy website sitting before centralized platforms like nmpjs.com?), then this info could be there instead.