MDN Web Docs
Replies: 0 comments 13 replies
-
|
@wbamberg That's cool. I've been looking at Learn/Server-Side and Glossary as a background task when my brain is gone. While I'm going to continue on those, they're a fallback, not a main task. So anyone else who wants to work on them before I get them done is quite welcome to do so. |
Beta Was this translation helpful? Give feedback.
-
|
Tracking bug for HTML: mdn/content#8961 |
Beta Was this translation helpful? Give feedback.
-
|
Tracking bug for SVG: mdn/content#8969 |
Beta Was this translation helpful? Give feedback.
-
|
@ddbeck , @caitmuenster , @rebloor : as you might know we're currently converting MDN docs from HTML files into Markdown. One of the big areas left is the add-ons docs: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons . I'm happy to do this conversion if you like (will ask for review from Richard and anyone else you like) but since you are the primary maintainers of these docs I think you should get to say whether you want them in Markdown, or would prefer that they stay in HTML. I'm happy to talk about the implications of making this change, either in a chat or in this discussion. I'm not sure how much it helps, but there is a page explaining what the new format is like: https://developer.mozilla.org/en-US/docs/MDN/Contribute/Markdown_in_MDN . FWIW I think conversion to Markdown would be a good thing for the Add-ons docs, and as far as I can remember there shouldn't be any big problems with the conversion. |
Beta Was this translation helpful? Give feedback.
-
|
@ddbeck , similarly to https://github.com/mdn/content/discussions/8960#discussioncomment-1410619: do the maintainers of the devtools documentation (https://developer.mozilla.org/en-US/docs/Tools) want it in Markdown? The same applies: I'm happy to do the conversion but don't feel like I should make the call about whether it is desirable. |
Beta Was this translation helpful? Give feedback.
-
|
Consensus is not to convert the Tools docs. |
Beta Was this translation helpful? Give feedback.
-
|
Tracking issue for Learning Area: mdn/content#9218 |
Beta Was this translation helpful? Give feedback.
-
|
Tracking issue for Glossary: mdn/content#9361 |
Beta Was this translation helpful? Give feedback.
-
|
Issue for web/accessibility (I think?) mdn/content#9631 |
Beta Was this translation helpful? Give feedback.
-
|
Tracking issue for WebAssembly: mdn/content#9721 |
Beta Was this translation helpful? Give feedback.
-
|
Tracking issue for Mozilla/Add-ons: mdn/content#9842 |
Beta Was this translation helpful? Give feedback.
-
|
Tracking issue for Mozilla/Firefox prep: mdn/content#9925 |
Beta Was this translation helpful? Give feedback.
-
|
PR for Games conversion: mdn/content#9659 |
Beta Was this translation helpful? Give feedback.
-
After mdn/content#8741, this spreadsheet: https://docs.google.com/spreadsheets/d/1gIW85rRxPkgsGjYw_5wLa_kGgMeOgnfYrpWytOMD8Lw/edit#gid=0 lists the remaining HTML files. I'm going to propose we convert the rest in the following sections, in the following order:
I'll file a tracking bug to prep and convert each of these areas.
Note that this excludes mozilla/projects/nss and devtools, which we don't maintain and which we plan to remove from MDN, as I understand it: (NSS reference: mdn/content#2669, devtools reference, a less definitive: mdn/content#8215 (comment)).
I believe other people have expressed an interest in (and actually started the work of) converting some of these areas. If so I'd be happy for you to claim these areas in responses to this post.
Update: removed devtools from the list.
Beta Was this translation helpful? Give feedback.
All reactions