Web Platform Docs Debuts with Developer Resources

  • 發行項

Today, we are taking another step forward in helping developers achieve the goal of interoperability through same markup. We’re happy to be part of creating Web Platform Docs (WPD), a new W3C hosted community resource for developers and designers who use open Web standards. For developers the Web is about building great experiences with the potential to reach millions of people around the world by writing interoperable sites and applications. We’ve talked many times about the promise of interoperability through the same standards-based markup yielding the same results.

Web Platform Docs (WPD)

The W3C, Adobe, Apple, Facebook, Google, HP, Microsoft, Mozilla, Nokia and Opera have teamed up to create and seed this new community-driven site whose aim is to become a central repository for Web developer documentation.

  • Clear reference docs that are accurate, complete, and indicate adoption rate.
  • Thoughtful tutorials for existing and new technologies.
  • A sample library that takes into account real-world scenarios.
  • The ability to see—at a glance—which technologies are on a standard track and the stability and implementation status of features.

WPD uses MediaWiki as its platform, and in the model of Wikipedia, WPD’s strength comes from a global assembly of volunteer developer contributors. Anyone can become a member, anyone can contribute, and the resulting community creates and manages the content through collaboration and mitigation. The W3C is the site’s convener and administrator. The founding organizations (and others who wish to join with financial support for the project) are known as stewards. The stewards help in infrastructure decisions and will have members act as contributors with the same rights as every other member who joins on their own. The stewards seeded WPD with topics donated from already-published content (over 3,200 topics from MSDN) and will continue to add content moving forward.

We view this as an opportunity to combine our information with that of other creators of developer content in a way in which the whole will become greater than the sum of its parts. Having developer content assembled in WPD means the data that’s important to your planning is centrally located and accurate. You won’t have to look at competing sites and wrestle with conflicting information. At the same time, evolving or proprietary APIs will be included, and they will be clearly marked as such. And when a topic is missing information or contains an error, you can flag it for a community member to update—or do it yourself.

It has been a pleasure and an honor working with our global and diverse partners in making this site a reality, and this is just the beginning for WPD. Creating a comprehensive standard reference library that drives standard adoption will take an ongoing concerted effort. We believe that part of building a highly interoperable Web browser means providing developers with the resources to achieve an environment where the same code and markup delivers the same results. And that makes the Web better for everyone.

— Eliot Graff, Content Publishing, Internet Explorer

Comments

  • Anonymous
    October 08, 2012
    Excellent!  Count me in...

  • Anonymous
    October 08, 2012
    +1, happy to see this rare collaboration between Microsoft and Google. Keep it up.

  • Anonymous
    October 08, 2012
    The comment has been removed

  • Anonymous
    October 08, 2012
    I hope WebGL dies a horrible death and no one tries to put my games in a browser ever again.

  • Anonymous
    October 08, 2012
    I'm fine with this as long as Microsoft doesn't fill these resources up with their UPPER CASE TAG MESS or their camelCaseAttributeGarbage... And if they do it needs to be immediately edited... This is the primary reason MSDN documentation is the worst available on the web.

  • Anonymous
    October 08, 2012
    Nice, 8 Errors, 1 warning(s) : validator.w3.org/check Wonderful, 5 Errors, 1 warning(s) : validator.w3.org/check

  • Anonymous
    October 08, 2012
    @David, first of all CamelCaseAttributes not the camelCase... and well-elaborated, vast MSDN library compared to... what exactly? Secondly thanks for letting us know that you are yet another troll against Microsoft corporation with "Everything developed by Microsoft is a garbage" kind of mentality. Such a good troll against MSFT, you might get yourself hired at Google (if you are not already working for them). You must be really ashamed of yourself for the times when you used products developed by MSFT; Windows OS, CE OS, XBox, Visual Studio, or even AVI file format etc etc... Hey, do yourself a favor and don't bother to come back here. Tip: communities like engadget, slashdot and google etc. do share your thoughts and these are some good places to promote your anti-MSFT propaganda.

  • Anonymous
    October 08, 2012
    ^ Ronald. Recognises troll, responds anyway in fury

  • Anonymous
    October 09, 2012
    The comment has been removed

  • Anonymous
    October 09, 2012
    The comment has been removed

  • Anonymous
    October 09, 2012
    @Olivier: Now run the validator on google.com or mozilla.com ;)

  • Anonymous
    October 09, 2012
    The comment has been removed

  • Anonymous
    October 10, 2012
    The comment has been removed

  • Anonymous
    October 11, 2012
    @Brian, @David I am working for an organization which is working closely with RedHat at NYC. But admittedly, MSDN documentation is one of the greatest repository for developers. The WORST examples Brain has filtered from over 10,000,000 pages doesn't invalidate/void the relaibility of MSDN. Now tell your employer Google to come up with something really tangible examples and tools to troll against Microsoft.

  • Anonymous
    October 11, 2012
    Glad to see that MSDN documentation failures are making it to the surface!  Even if Microsoft doesn't contribute them they can at least spend some time to re-vamp them correct all the errors and make them at least useful for once! Whenever I see a fellow developer (that isn't trying to solve an IE-only bug) on MSDN I've had to stop and make sure they were only reading it for humor not for actual facts examples and advice.

  • Anonymous
    October 11, 2012
    Release the Internet Explorer 10 for Windows 7! Please hurry.

  • Anonymous
    October 12, 2012
    Just kidding. Actually MSDN documentation is first class. Since I am not a developer nor a professional, so I don't know anything about it.

  • Anonymous
    October 14, 2012
    The comment has been removed