FOR DISCUSSION: This document not finished elaborating, you can see the feedback in the Vision document in Google Docs
Serve feature compatibility information across multiple outlets and formats without data duplication
The production vision document is about making a consensus about the features and limitations of the product. It should help us by providing a common vocabulary to help better communicate throughout the phases of the project.
Project Vision document defined by the Scrum Alliance and Agile Manifesto as a guideline to structuring work without overdoing it.
1.1. See also
- Compatibility Data product vision (this document)
- Compatibility Data: A Shared Resource (2015 slides deck)
- Functional dependencies analysis
- High level feature prioritization worksheet
- Tribal knowledge
Compatibility data 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.
For Web Developers, Who wants to know if they should use a technique, The BrowserCompat system is a specialized web service, That provides compatibility data Unlike caniuse.com We'll be able to have a usable maintenance flow serving reports in multiple formats
1.3. Production vision summary
An overview, summarizing this document
Note: This table is purposefully rough-grained, giving an overview of what we’re building, what it’ll do, and for whom.
2. Business Opportunity/Problem Statement
Not finished yet, see Vision document in Google Docs