Re: Standardization status

The only reason i brought this up as i viewed these on my phone this
morning and wasn't sure what they each stood for. And i agree, a legend
isn't the solution as having to navigate to another page just to view it
won;t work.

Just a thought, what about something like wrapping the text around the
indicator stating what it stands for, something like this [1]? Having it
split up around the top and the bottom? I will try do a quick mock-up later
today with the examples you sent to see how it looks.

[1] http://codepen.io/chriscoyier/pen/circle-type/

// Nic da Costa


On 11 July 2013 08:31, Lea Verou <lea@w3.org> wrote:

> Hi Nic,
>
> Glad you like it!
>
> You are raising a very good point. Honestly, I don’t know. :( Suggestions
> welcome.
>
> Eventually these statuses will link to pages explaining what they mean, so
> at least that will be some help. Although, you certainly shouldn't need to
> load another page just to find out the status.
>
> Perhaps we could have a legend somewhere for now? I don’t like this
> solution because most people won’t look at it, but it’s better than nothing.
>
> Doug, since it was your idea, perhaps you’ve thought about this?
>
> Cheers,
> Lea
>
> Lea Verou
> W3C developer relations
> http://w3.org/people/all#lea ✿ http://lea.verou.me ✿ @leaverou
>
>
>
>
>
>
> On Jul 11, 2013, at 09:18, Nic da Costa <njr.dacosta@gmail.com> wrote:
>
> Hey Lea
>
> They look awesome! I really like them.
>
> Is there a key on one of our pages indicating what each indicator means?
> As currently to determine what the indicator is ( *if you aren't already
> familiar with them *) you have to hover over them, but what if this is
> mobile or other touch devices? How are new user's going to know what the
> indicator stands for?
>
> Otherwise i think they look great!
>
> // Nic da Costa
>
>
> On 11 July 2013 06:54, Lea Verou <lea@w3.org> wrote:
>
>> A few days ago Doug asked me to redesign the standardization status
>> ribbon, because it was misleading and too obtrusive.
>> A very good point he made was that we should indicate what each status
>> means, not just the name. For example, many people don’t know that Proposed
>> Recommendations are more mature that Candidate Recommendations or that an
>> Editor’s Draft comes before a Working Draft.
>> So, we worked together on a standardization status that looks more like a
>> progress indicator for W3C statuses. Today I worked a bit on the other,
>> non-W3C statuses as well, so I wanted some feedback.
>>
>> Here’s a dabblet with all statuses: http://dabblet.com/gist/5922066
>>
>> And here are various statuses in context:
>> ED: http://docs.webplatform.org/wiki/OLD:css/cssom/CSSRegionStyleRule
>> WD: http://docs.webplatform.org/wiki/css/properties/shape-outside
>> LC: http://docs.webplatform.org/wiki/css/functions/var
>> CR: http://docs.webplatform.org/wiki/css/properties/border-radius
>> REC: http://docs.webplatform.org/wiki/css/properties/font-size
>> Deprecated: http://docs.webplatform.org/wiki/html/attributes/lowsrc
>> Experimental:
>> http://docs.webplatform.org/wiki/css/properties/shape-inside
>>
>> Also, I realized W3C Proposed Recommendation is not in the allowed
>> statuses [1]. Someone should add it. I’d do it myself, but I’m not sure how.
>>
>> [1]: http://docs.webplatform.org/wiki/Property:Standardization_Status
>>
>> Thanks!
>>
>> Cheers,
>> Lea
>>
>>
>> Lea Verou
>> W3C developer relations
>> http://w3.org/people/all#lea ✿ http://lea.verou.me ✿ @leaverou
>>
>>
>>
>>
>>
>>
>>
>
>