The WebPlatform project has been discontinued when the Stewards partnership agreement ended in September 2015. This site has been frozen, and the assets we have created will remain.
spec status representation
Representing the status of a spec
One problem we currently have on WebPlatform is that we lack a decent representation of how usable a feature is in the real world. Currently we show an entry for W3C spec status at the top of each feature's page, and we also have a section further down called "Related specifications", which shows what specifications the feature is defined in, what W3C rec level these are at, etc. See http://docs.webplatform.org/wiki/css/properties/font-size for an example
The problem is that recommendation status is not immediately useful to the average developer on the street, who just wants to know if they can use this feature in their real world projects now. There are plenty of features defined in W3C recommendations that are not supported across all browsers! The current way of doing things is also repetitious.
These pieces of data are related, but definitely separate.
A potential solution
So we need a solution that will fulfil both aims:
- Give developers a definite measure of whether they can use a feature now in their production work
- Inform developers as to what specs the feature is defined in, so they can find out more information from the specs if needed
I think the current page features we have in place solve number 2 nicely, but I think we should get rid of the W3C spec status that appears at the top of the page. It is repetitious, and looks fugly!
For number 1, I think we should have an easily defined metric that indicates whether developers should and could use each feature now. This should go up the top of each page, in the same place that the W3C rec status currently is (or perhaps as an entry in the details table just below that). We should use a nice bedging system like they use on http://html5please.com/
I would call it something like
- production ready?
And the values I'd give it are as follows:
- "Proprietary: Used in XXXX" (where XXXX is the proprietary browser feature. So for example "Used in Chrome extensions" or "Used in styling Windows 8 apps")
- "Avoid" (where the feature is only supported across one or two browsers, and/or no easy way of Polyfilling or fallback exists and/or the spec is unstable so the syntax is likely to change 4 times in the next 3 months)
- "Use with polyfill" (where the feature is supported across all modern browsers, and polyfills exist for providing support in older browsers)
- "Use with fallback" (where the feature is supported across all modern browsers, and it is easy to create a fallback for older browsers, and/or the feature gracefully degrades)
- "Use" (the feature is as old as the hills, and supported everywhere)
So in this classification, we are not explicitly saying anything about a feature's spec status or stability, just if it is usable now or not. Stability, etc. can be gotten from the related specs. If we wanted to give more details, we could give a further info box where we can say why the feature is "Avoid" or "Use with Polyfill". A link to the Polyfill might be nice in the latter case.
Related bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=20386