Live data from Hacker News

Documenting the Web together

blogs.windows.com

111–120 of 212 posts

Re: Documenting the Web together

#111
post #77

We were speaking about this at the W3C's Advisory Board meeting in London earlier this week. It distresses me that the specs on w3.org are so hard to read for the average developer. It's great to see how MDN focuses on simplicity, readability, and usable examples.

MDN resources are written for web developers (ie. consumers of the already implemented language spec). The W3 spec has to be written for its implementors and is necessarily much more complicated.

Re: Documenting the Web together

#113
post #76

> One of our guiding principles in developing Microsoft Edge is that end users should never have to worry about which sites work in which browsers. This philosophy—”the Web should just work for everyone“—led to our choice to target the “interoperable intersection” of web APIs in our browser engineering. That's a good move by MS. In this context it's great to see them supporting open codecs, and for istance OGG contai…

Yet here I am and still have to fight flexbox bugs in IE 11 they were too lazy to fix for 2 years and then closed the ticket because IE 11 was legacy at that point.

Re: Documenting the Web together

#114
post #81

Don't forget you can use https://devdocs.io/ too which also searches MDN and store offline. The two are a great pair.

cool, i didn't know that site. wonderful ux how's the content added though? its missing so many libraries i use...

They have a Trello board where you can suggest and vote on additions. https://trello.com/b/6BmTulfx/devdocs-documentation

Re: Documenting the Web together

#115
post #99

mdn.com is of course a 90s directory site for Muslims in Dearborn, Michigan. last updated by the looks of it in early 2016... maybe they'll relinquish the vanity domain?

What makes it a vanity domain?

Just imagine how much printed material has circulated since the 90s with the mdn.com address. Why do you want to break the web?

Re: Documenting the Web together

#118
post #10

This is a great start. Now let's integrate caniuse into every single MDN page.

MDN already has compatibility tables for lots of things; if they're missing from a particular article, it's not because they're unsupported, it's because nobody has done the research and filled in the information (it's a wiki! You can add things!).

No need to duplicate the effort though, caniuse usually links to MDN for feature reference anyway.

If caniuse had embeds, they could easily replace the existing compat tables on MDN.

Re: Documenting the Web together

#119
post #77

We were speaking about this at the W3C's Advisory Board meeting in London earlier this week. It distresses me that the specs on w3.org are so hard to read for the average developer. It's great to see how MDN focuses on simplicity, readability, and usable examples.

[deleted]

Re: Documenting the Web together

#120

Déjà vu. Previously ( checks email …almost exactly 5 years ago?! Christ, it was a long time ago), the web powers that be announced they were going to collaborate on a new web docs wiki.[0] I don't think it went anywhere because, well, MDN already existed. I'm glad they finally just surrendered to MDN, even if it was many years late. [0] https://www.w3.org/2012/10/webplatform.html.en

They chose a different license that made it more difficult than it should have been to integrate content from MDN. The two sites' backends were completely different, too, so the source texts needed to be tweaked before publishing. I also remember that for for many of the docs, they favored basing them off MS's contribution (IIRC). It also had a very un-wiki-like atmosphere, where the lifecycle of a change resembled a code review, i.e., the opposite of the "be bold" policy that led to the success of Wikipedia (and the early days of developer.mozilla.org).
Post reply on HN