Earlier quoted context omitted.
I've never understood the hate for w3schools. I've always found them to be extremely useful. I like that usage examples is the focus of their site. I find that more useful than wordy documentations that more advanced references provide.
http://www.w3fools.com/ top of the page summarizes the situation: > When W3Fools was launched in 2011, the state of documentation for developers was poor. This site documented many content errors and issues with the W3Schools website. The Mozilla Developer Network was around but it did not have much support at the time. > Today, W3Schools has largely resolved these issues and addressed the majority of the undersigned…
Documenting the Web together
61–70 of 212 posts
Re: Documenting the Web together
#62Good Bye w3schools.com ?
w3schools.com is a great resource. I prefer it when I need a quick refresher on an HTML element because it's especially good for having short, simple examples I can copy and paste. MDN tends to be verbose and technical. It's good when you need to know everything in detail, but often I need a quick refresher and a simple example and for that w3schools.com always seems to have better content. Compare these two pages fo…
tags (yuck) after them are ok (label tags add accessibility among other things).
tl;dr: use 's with 's, not plain text labels, as MDN shows you to do.
Re: Documenting the Web together
#63Re: Documenting the Web together
#64Good Bye w3schools.com ?
w3schools.com is a great resource. I prefer it when I need a quick refresher on an HTML element because it's especially good for having short, simple examples I can copy and paste. MDN tends to be verbose and technical. It's good when you need to know everything in detail, but often I need a quick refresher and a simple example and for that w3schools.com always seems to have better content. Compare these two pages fo…
Re: Documenting the Web together
#65Great, while they are at it can Google please downgrade the extremely spammy w3schools or at least allow me to remove certain websites from my searches. There are so many better resources out there...
I’ll never/rarely click a w3schools link, but I do find MDN to be quite difficult to read with it’s pages being quite technical and terse. W3schools is quite pragmatic with providing a reference for CSS properties. I hope these extra resources will let MDN improve on this.
Re: Documenting the Web together
#66Great, while they are at it can Google please downgrade the extremely spammy w3schools or at least allow me to remove certain websites from my searches. There are so many better resources out there...
> or at least allow me to remove certain websites from my searches. Im currently using a chrome extension from google[0] to do exactly this. [0] https://chrome.google.com/webstore/detail/personal-blocklist...
Google is tracking everything about me. So I expect that certainly they can track which sites I don't like, especially when I mark them as such.
Re: Documenting the Web together
#67Great, while they are at it can Google please downgrade the extremely spammy w3schools or at least allow me to remove certain websites from my searches. There are so many better resources out there...
I've never understood the hate for w3schools. I've always found them to be extremely useful. I like that usage examples is the focus of their site. I find that more useful than wordy documentations that more advanced references provide.
Re: Documenting the Web together
#68This news sounds great to me, but I feel like I don't understand what's happening behind the curtain and don't grasp the second-order consequences. What would motivate them? I wonder what the political motives are (industry politics, not the other kind that we won't mention here). Could this eventually displace standards bodies such as WHATWG and W3C? If the Product Advisory Board of Mozilla, Google, and Samsung agre…
Re: Documenting the Web together
#69Earlier quoted context omitted.
I’ll never/rarely click a w3schools link, but I do find MDN to be quite difficult to read with it’s pages being quite technical and terse. W3schools is quite pragmatic with providing a reference for CSS properties. I hope these extra resources will let MDN improve on this.
I agree. I feel like going to MDN to quickly look up syntax is like trying to kill a fly with a handgun.
For super quick syntax checks ("Is it fill-opacity or opacity?") MDN might be a little overboard, but as any sort of reference beyond 3 line snippets it is the link that I always look for. I usually append MDN to the end of my searches for HTML/SVG help.