-
Notifications
You must be signed in to change notification settings - Fork 76
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
Explainer is out of date. Should we remove it? #622
Comments
MDN is pretty good for more settled pieces, and usually the other parts are chrome-specific so the Chrome documentation is fine. |
Yeah, I'm wondering if we should invest more into making the MDN article really good. |
The MDN article was the most helpful thing I found when i was spinning up on this. Seems like a good resource to continue to maintain. |
yi-gu
added a commit
that referenced
this issue
Sep 5, 2024
This explainer is out of date and per #622 we have been using the following resources. Removing the explainer to reduce confusion. The spec is certainly up to date with Chrome's implementation, but it is probably harder to read than what we'd want to point developers too. Chrome's developer documentation is also up to date, but we probably want something Chrome-agnostic. MDN's developer documentation is chrome-agnostic, but not as up to date as Chrome's.
npm1
pushed a commit
that referenced
this issue
Sep 18, 2024
This explainer is out of date and per #622 we have been using the following resources. Removing the explainer to reduce confusion. The spec is certainly up to date with Chrome's implementation, but it is probably harder to read than what we'd want to point developers too. Chrome's developer documentation is also up to date, but we probably want something Chrome-agnostic. MDN's developer documentation is chrome-agnostic, but not as up to date as Chrome's.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We wrote a series of explainers over the years, but most of them are fairly out of date at this point, as @yoavweiss noted here #621 (comment).
The spec is certainly up to date with Chrome's implementation, but it is probably harder to read than what we'd want to point developers too.
Chrome's developer documentation is also up to date, but we probably want something Chrome-agnostic.
MDN's developer documentation is chrome-agnostic, but not as up to date as Chrome's.
We should probably remove the explainer (or at least mark it as out of date), but that leaves us the question: where should we point developers to?
The text was updated successfully, but these errors were encountered: