-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MDN URL per feature #1122
Comments
I toyed a little bit with this on this dashboard I made: https://captainbrosset.github.io/web-features-explorer/recent/ I don't think that's what you wanted here, but I thought I'd mention it anyway. This could be a solution that doesn't require maintenance. |
We could quite easily generate |
I guess we could also map markdown articles in the mdn/content repo to web-feature IDs, like we do in BCD. |
I think this has gotten a lot more tractable now that mdn/browser-compat-data#23431 (and attendant fixes) has landed. Starting with the next BCD release, we can expect BCD's So I'd probably suggest a strategy like this:
Alternatively, we could use the MDN content inventory directly instead (e.g., finding pages that cite the feature's compat keys in frontmatter). This is more likely to find overview pages (e.g., Clipboard API — I don't think any BCD object links to pages like this), but won't be as strict (any arbitrary page can have a compat frontmatter key). |
In order to support GoogleChrome/webstatus.dev#295 we'd need a MDN URL per feature and publish it as
mdn_url
or similar.We can get MDN URLs from BCD, but for most features we'll have more than one. If so we need to pick one of them, or sometimes another page that's about the feature as a a whole.
cc @estelle
The text was updated successfully, but these errors were encountered: