Replies: 1 comment
-
It will be good to have section of MDN for obsolete content that store different features for historical purposes, but I think this will require a lot of work and separate section from other content so as not to confuse someone who is looking for solution of their problem on MDN. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We recently had a new issue opened about
<menuitem>
that asks for the page (and API page) to be removed: mdn/content#32458. I took a look and would quote my reply here for convenience:I discovered that we had this conversation before and it was decided to keep the pages in mdn/content#24886. Unfortunately, the rationale for keeping the pages is not visible any more, so I'm opening a GitHub Discussion so there's a record.
The question is: Is it valuable to keep this information for historical purposes as an exception to our usual policies, or is it time to remove the content?
Looking forward to hearing what you think!
Related issues and PRs:
Beta Was this translation helpful? Give feedback.
All reactions