webstatus.dev

webstatus.dev copied to clipboard

We often hear from developers that they'd like to be able to see all the features that achieve a certain "thing" or certain business outcome, and to know which should be treated as progressive enhancements vs. that are interoperable. It would be great to have a set of labels or filters that allow developers to view only features within this category.

Some example filters

• UI / Visual effects
• Loading / performance
• Media
• Web apps

Thanks for suggesting this @hvanops!

We are looking at storing the group field from the web-features data and after storing that, we could offer a filter for that.

Could you take a look at the values there and see if they would meet your requirements?

If not, you could:

• Ask the folks in the web features repository if they would allow you to add a new field with this information (since we already consume that info)
• Let us know about another source of truth which has your information that maps back to features.

Hopefully that helps!

cc: @foolip @atopal

I think the group field is a good place to start.

Is there a set list of what the group field could be? I couldn't tell at a glance, and am not too familiar with this otherwise.

This is something that is actively being discussed in this issue. https://github.com/web-platform-dx/web-features/issues/532

They should be able to discuss your use-case and give you more details on the naming!

In the meantime, you can find the current groups here.

I have a draft PR to publish groups in web-features in https://github.com/web-platform-dx/web-features/pull/1060. We'd also need guidelines on what should be a group and what should be a feature, which is a rather hard problem.

The groups we've added so far in web-features (but aren't published) are more like a taxonomy tree of the platform. Another approach would be more like tags that don't have any structure and can overlap in any kind of way.

@hvanops which would you say is the most important group you'd like to track? If that fits in a tree we can pursue that, but if not it suggests we should think again about tags as an alternative approach.

I'm assuming that there will be more of those groups than we'd like to add to Web Features, I filed issue #297 to add a way to create a filter for arbitrary features within the dashboard instead.

@hvanops Do you think #297 will cover your needs? If so, I will close this issue in favor of that one. If not, I will keep this one open.

Hi,

So sorry for the delay on this. I think #297 should cover our needs, and would just be a different keyword from what atopal suggested in the original issue.

On Wed, May 29, 2024 at 10:41 AM James C Scott III @.***> wrote:

@hvanops https://github.com/hvanops Do you think #297 https://github.com/GoogleChrome/webstatus.dev/issues/297 will cover your needs? If so, I will close this issue in favor of that one. If not, I will keep this one open.

— Reply to this email directly, view it on GitHub https://github.com/GoogleChrome/webstatus.dev/issues/276#issuecomment-2137587377, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV2BPB4NCGLPLG2U7Q357U3ZEXSJVAVCNFSM6AAAAABHWHBV6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXGU4DOMZXG4 . You are receiving this because you were mentioned.Message ID: <GoogleChrome/webstatus.dev/issues/276/2137587377 <(213)%20758-7377>@ github.com>

Hi @hvanops! Now that we support #297, we can close this, right?

Yep! Looks great to me. Closing with this comment. Thanks.