How to proceed for the removal of the old compat table macros? #73
Replies: 2 comments
-
|
(pinging @mdn/localization-team-leads) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Cross-linking to mdn/translated-content#5618 |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, @mdn/localization-team-leads!
Last year, on mdn/content, we removed the old compatibility tables and replaced the mess of HTML tables and odd macros with a single macro, reading the data from mdn/browser-compat-data, with a key set in the Yaml header of the page.
We have now in mdn/yari a bunch of macros, no more used at all on mdn/content but that have more than 1000 occurrences in mdn/translated-content:

(and
{{property_prefix}}too)How to remove these efficiently?
My 2 🪙 :
Maybe we should remove the Browser compatibility and Specifications sections of all translated pages, add the Yaml
spec_urlkey in mdn/content and replace them with the two macros, like in mdn/content.I think this would improve a lot the quality of the translated pages while helping get closer to actually deleting these macros.
This is just an idea, a conversation starter, so feel free to comment!
Beta Was this translation helpful? Give feedback.
All reactions