Thanks @Elchi3 , I'll have a look at this soon.

To answer your question, the version of kumascript inside the yari repo is the one to update. The kumascript repo will be archived soon.

Thanks Chris, I will open a PR against Yari then.

For the record, the repo is open for merges now.

I set this to Draft status under the assumption that we don’t want it to end up getting merged until the SpecData change is merged and deployed. Did I assume correctly?

I set this to Draft status under the assumption that we don’t want it to end up getting merged until the SpecData change is merged and deployed. Did I assume correctly?

The page builds without the macro change, so I'm not sure what the policy is. I've sent mdn/yari#2147 now. If needed, someone can review and merge that one first.

The page builds without the macro change, so I'm not sure what the policy is.

Yeah I guess we should have a documented policy. But at it least seems like if the change gets deployed to production with the new macro also having been deployed, the resulting user experience for readers of the article is no ideal — I mean, given that the spec reference would then just show up as Unknown, without the actual intended link to the spec.

I guess the procedure in that case is just to make sure the correc spec details are there before the content pr is made. I'll write something up.

The Yari PR was merged. This is ready

merged!