Leading W3C Developer Tools to their full potential
Allow me to introduce myself, my name is Guillaume Baudusseau and I'm a Computer Science student who will be spending the next year at W3C working on the Developer Tools. Passionate about the Web and its community, I want to provide a new developer experience on W3C's tools. This blog will be to share with you some news on these tools. Captivating things are happening, just have a look.
To start, W3C is seeking to revitalize the Developer Community around its existing tool set. Many are already familiar with our validators and we have had some significant contributions the open source over the years.
We are looking at ways to be more inclusive and simplify how you may contribute, for example:
We also want to create an environment that is welcoming to new developers and for them to be able to seek answers from the more knowledgeable members of the community on how to use web technologies. We will let you know more in the next articles.
We look forward to reading your suggestions or comments here.
Guillaume
I've written fairly strict standards based markup since getting into Web Design and Development about 6 years ago as a student and more professionally in recent years. However, away from what is publicised by education networks like Lynda and Tuts+ I'm a little in the dark about web standards and how each standard set by W3 comes to be, is implemented and how it effects the open web.
That said, I recently read some proposed specs and working drafts published via W3 news which still left me slightly in the dark. Practical examples are useful to me and I look forward to viewing related Github repos and pages for updates.
Best regards for your time with W3 and future studies.
Hi Alistair!
Thank you for reading. Maybe you can have a look at http://www.w3.org/standards/about.html
Regards
I'm glad this is moving in this direction, I was looking a while back to get the Unicorn validator to be a command line tool that could be interfaced much like Eslint. That way when developing an application I could run real time validations of all CSS and HTML from the return of a server.
Things that would be nice once you have resolved your goals are:
- Making a pluggable interface for being able to add in custom element validation or new parse features
- Expose low level tokens used by parser
- Adding in pluggable interface for custom rules / concede other rules that are native.
- Hook in some of the unit tests specs have into future releases of the validator
Guillaume, I love this idea! We are planning some of the same things for MDN in 2015 - i.e., tools and services to help developers validate cross-browser compatibility, accessibility, and security. We should Skype sometime about how to collaborate.
That's a great initiative, thank you!
Moving the code repositories to Github is a good idea, it will give greater visibility and make it easier to submit contributions.