mdn
What does not work
Docs are great in reference form. Clear and concise. In practical terms, nothing ever works as simply as reference docs might imply with their 'perfect world' context.
Adding links to content elsewhere that add real world experience context to articles will help people get a fuller perspective of how to actually use the reference in real life.
Summary
Add a link to a relevant third-party article.
Motivation
Help developers get a fuller perspective of how CSS Custom Properties work in reality.
Preview URLs
Flaws
None! 🎉
External URLs
URL: /en-US/docs/Web/CSS/Using_CSS_custom_properties
Title: Using CSS custom properties (variables)
on GitHub
- https://css-tricks.com/the-big-gotcha-with-custom-properties/ (1 time) (Note! This may be a new URL 👀)
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I think better than adding a link would be to incorporate the issue addressed in the CSS-Tricks post into the content of the custom properties overview page. The main issue is CSS elements inherit the results of a function, not the actual function, so there is no down-the-line ability to change a parameter value. We should make this clear in the text rather than linking to an article that shows examples but doesn't actually seem to state the issue.
Is this something you would be up for doing or creating an issue so someone else does it?
@inspector71 What do you think about https://github.com/mdn/content/pull/19042#issuecomment-1203183192?
