Project statement
Currently, contributing to Browser compatibility table is somewhat bloated:
- Data are not centralized : it is difficult to reuse the same data on different pages and keep them all up to date.
- Compatibility tables don't scale well : it is almost impossible to have more than 5 browsers in the table at the same time and the responsiveness of the tables are not very good in the new design.
So there is room for improvement and there are many issues that need to be solved :
- How to store the data (technicaly speeking)
- How to design the data in order to have a scalable database
- How to improve the display of the data and make it more accurate and more scalable in a design point of view.
- How to ease data contribution (automated and/or manually) which is both a technical (for the automated part) and UX (for a manual contribution) issue.
Ressources
- Proposal by David Bushner to automated gathering compatibility data
- Draft for a data schema by Sheppy, Jean-Yves and Jeremie
- Other possible ressources:
Next steps
- Start gathering use cases and clear the needs around compatibility tables
- Sort out a plan with steps and goals
- Kick off the project with MDN, Kuma and UX lead