-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Add page-type to Web_component and relocate them #26173
Conversation
Preview URLs (51 pages)
Flaws (40)Note! 42 documents with no flaws that don't need to be listed. 🎉 URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
External URLs (10)URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
(comment last updated: 2023-04-13 21:16:19) |
This is incongruous under Web/API as well though, isn't it? AFAIK this is the only I think we should decide whether it's a |
I would see it as a |
Fair enough, I'm happy with that for now. I think the underlying issue here is that we have this IA in Web/API in which top-level things are supposed to be "Web APIs", narrowly conceived as things that map to specifications, but then we quite often want to talk about higher-level concepts that cut across "Web APIs", narrowly conceived, and we don't have a systematic way to present these. See also, things like the PWA docs and to a lesser extent the new Performance API docs. Some day we will need to resolve this. |
I think we will be able to resolve this the day we can have the Divio system applied at the top level. For this, we first need to clean the top level, though. |
This pull request has merge conflicts that must be resolved before it can be merged. |
This will also need:
...in groupdata.json, or it won't appear in https://developer.mozilla.org/en-US/docs/Web/API and the sidebar won't have the name at the top: I'm still a bit uncomfortable having this in Web/API, but I take the point that we don't have a perfect solution here. |
I agree: I think we won't have a good solution until we can apply the DIvio system at the top level. I really want to finish all the refactoring that started a few years ago so we can start working on this question later this year. I think there are too many things getting in the way for the moment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @teoli2003 !
* Add page-type to Web_component and relocate them * Fix flaws * landing-page -> web-api-overview * Fix links – yarn content move should do this * Actually remove the files * Add overview page to GroupData
As part of openwebdocs/project#91 we adds page-type to every document on MDN.
This PR adds them (landing-page and guide) to the documents under Web/Web_components.
In addition, it relocates the folder under Web/API. Its location at the top of the Web/ hierarchy is incongruous: It is a set of APIs. Its sidebar was
{{DefaultAPISidebar}}
and usedGroupData.json
anyway.