Skip to content
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

Open
samuelgoto opened this issue Jul 3, 2024 · 3 comments
Open

Explainer is out of date. Should we remove it? #622

samuelgoto opened this issue Jul 3, 2024 · 3 comments

Comments

@samuelgoto
Copy link
Collaborator

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?

@npm1
Copy link
Collaborator

npm1 commented Jul 3, 2024

MDN is pretty good for more settled pieces, and usually the other parts are chrome-specific so the Chrome documentation is fine.

@samuelgoto
Copy link
Collaborator Author

MDN is pretty good for more settled pieces

Yeah, I'm wondering if we should invest more into making the MDN article really good.

@aaronpk
Copy link

aaronpk commented Jul 3, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants