Replies: 1 comment
-
Thanks a lot for raising this one. There's a related discussion here about where to put inline macros: https://github.com/orgs/mdn/discussions/654 and I think moving this data up into front matter has come up before in discussion: https://github.com/orgs/mdn/discussions/254#discussioncomment-4232611 There is a lot of work ongoing relating to banners happening at the moment (availability in workers, experimental/status, baseline, etc.) and defining these via front-matter is going to be a consideration to help with authoring. I think we can bring this up again in the next community call to get some more feedback on it. Also relating to manually adding these macros, it might be worth checking with @OnkarRuikar if there's any overlap, since there is automation to add these in en content: |
Beta Was this translation helpful? Give feedback.
-
Hi all!
Recently I've been working on synchronizing the use of some macros in translations. This is a rather monotonous and necessary process)) Therefore, the idea arose to improve/automate the work with some macros.
I started looking for information about this problem and found (https://github.com/orgs/mdn/discussions/199#discussioncomment-618185, mdn/yari#350), but could not understand what conclusions we came to and why we were unable to implement such automation.
Therefore, once again I propose to consider the following:
1. Use information from the front matter instead of macros
Use information from the front matter
status
property instead of manually calling{{SeeCompatTable}}
,{{Non-standard_Header}}
and{{Deprecated_Header}}
macros to display appropriate banners.Advantages:
mdn/translated-content
there is no need to monitor the appearance/deletion of a macro inmdn/content
.Are there any advantages to manually adding banners?
Could there be a situation where the document has
status.experimental
, but we don't want to display the{{SeeCompatTable}}
banner (or vice versa)?2. Add new front matter properties
Add new front matter properties to replace the
{{AvailableInWorkers}}
and{{SecureContext_Header}}
macros and proceed by analogy with point 1.Beta Was this translation helpful? Give feedback.
All reactions