Closed axelav closed 12 years ago
Yeah, I was actually going to link to the spec. Your idea might be better, because MDN also includes browser support. If you want to tackle it, go ahead. The site is not actually up here on GitHub, but it's just a one page site, so you can just view source and edit it locally.
But the question is, where would I put this link, so it's not too cluttered. I don't really want to link the titles. Let me think about it and I'll see what works best in the design/layout. Thanks.
Perhaps it could just be a "more info" link at the end of the blurb? I'll play around with it some today.
A couple ideas:
I think I like the button best...
I think I like the button. I'll likely change the existing link to say "permalink", then add a button for "MDN" as well as "W3C spec".
But nothing definite yet; I'll see how it goes. Don't do any work on this, in case I change my mind. I just want to see it locally first on a few properties.
Thanks!
yup, that makes sense.
Took a few hours, but I've added links to MDN and the spec for all properties. All the W3C links are to the "dev" version of the spec (which is more up to date), but a few properties I couldn't find on dev, so they point to the TR version.
For the MDN links, I assumed the URLs are accurate, I didn't test all of them. Most should be fine. I'll close this issue now. Thanks for the suggestion, @axelav.
awesome, looks great!
Sometimes the little blurb of text isn't really enough. It would be great if each property had a link out to MDN (https://developer.mozilla.org/en-US/docs/CSS/background-attachment, for example) if further information is needed.
Also, I am happy to help implement this!