Web compatibility tables (WCT) are one of the key feature of MDN. It allows users to know more about the reliability of any web standard features and to ease the use of web technologies. Currently, the data are gather and maintain "by hand". Thanks to our awesome community we have some good data. However, this is hardly sustainable as the number of technologies is growing as well a the complexity of the implementation. We start to face some difficulties to stay up to date and to provide and improved content around those data.

Goals

This project intend to cover the following goals:

Improving the quality and display of data
- Avoid misleading users with inaccurate data.
  - NOTE: This is our primary concern as misleading users is the worst thing we could do on MDN (as a bad side effect it could induce distrust of Mozilla).
- Make sure our data are coherent all across MDN.
  - NOTE: This is our secondary most important concern for the same reason as the first one (even if the side effect could only affect MDN rather than Mozilla).
- Allow compatibility data to scale technically with a proper data schema
- Allow simple and complex compatibility data to be properly display in a responsive environment
Easing data contribution
- Allow (and automate) massive data contribution
- Allow easier single in-site contribution
  - NOTE: This is our third most important concern as it impacts contributors right now. By easing the contribution we ensure to improve both the quality and quantity of data, but we also pleased our contributors which ultimately contribute to the good reputation of both MDN and Mozilla.
Easing access to data
- Provide a way to allow third party tools or web sites to use our data
- Allow importation of data from third party resources
Allowing the reuse of data within MDN
- Make data reachable through KumaScript
- Make data usable for filtering research

NOTE: This project is action driven rather than time driven. It means that we do whatever is needed to reach our goals, whatever the time it requires. However, in order to not to be swamped into an endless project, we try to cut into small actionable steps that allows to measure progress as often as possible.

Critical Path

To ensure the success of the project, the following schema detailed its critical path in term of actions.

Critical path

It can be roughly summarized as follow:

Retrieve the most important needs (requirement and use cases) regarding the data
Handle a data storage
Build how to get data
Build how to expose data

Get Involved

Any one who wish to get involved with this project is welcome. This page will provide information about the project and its progress. Everything is discuss directly on the dev-mdn mailing list. Schedule and progress are summarized on the the mdn-drivers mailing list.

Jeremie is the resource leading that project, feel free to contact him for any question. He's available, for sure, on IRC every Monday (European time) on the various MDN Chanel (#mdn, #devmo, #mdndev) and more.