Re: readiness markers

I actually can't get on IRC right now. I don't hate "is Needs Work". "Needs
Work" is the state. "This article is [state]" isn't terrible.

Oh, crap, why isn't this discussion on the list? My mistake, I think, in
replying and not checking earlier. The past few emails in this thread are
quoted below.



On Thu, Jun 12, 2014 at 1:13 PM, Amelia Bellamy-Royds <
amelia.bellamy.royds@gmail.com> wrote:

> I just realized the problem with the "is Needs Work" -- join the
> brainstorm on IRC if you can.  Changing it in the template would be a
> hassle and poor coding practice.
>
> Can we think of something grammatically consistent?
>
>
> On 12 June 2014 11:10, Jen Simmons <jen@jensimmons.com> wrote:
>
>> Ok, I'll redo the CSS I wrote with Needs_Work for class names, instead of
>> needs-work.
>>
>> Yes, we want to remove the period. I'll let someone else change the
>> templates — whoever is deploying the CSS.
>>
>> We also need to remove the "note" class. We don't want any of that CSS
>> applying, and rather than override it all, I'd like to just remove the
>> class.
>>
>> The sentence should read:
>> *This article is *Ready To Use
>> *This article is* Almost Ready
>> *This article is* In Progress
>> *This article *Needs Work
>>
>> There is no "is" in the last sentence! Can we do that? I'd like to. It's
>> much better than "This article is Needs Work".
>>
>> I'll wait to hear other opinions on whether to make the icons white or
>> black. The text should be all black, it's better for color contrast
>> accessibility. The question at hand is about the icon color.
>>
>>
>> On Thu, Jun 12, 2014 at 12:53 PM, Amelia Bellamy-Royds <
>> amelia.bellamy.royds@gmail.com> wrote:
>>
>>> P.S.  One important but finicky detail:
>>>
>>> The template currently uses "Wiki encoding" to convert the text values
>>> of the states into a class name, which means that Needs Work would become
>>> "Needs_Work" not needs-work.
>>>
>>> It's not following standard CSS class naming conventions, I realize, but
>>> it made the templates much simpler (and means I don't have to change the
>>> templates to change the name!).
>>>
>>>
>>> On 12 June 2014 10:45, Amelia Bellamy-Royds <
>>> amelia.bellamy.royds@gmail.com> wrote:
>>>
>>>> Looks great, Jen.
>>>>
>>>> I second eliot's recommendation for the home page, to go with black
>>>> text on the lighter but still saturated versions of the colours.
>>>>
>>>> On the naming.  I like your suggestions (and just wish someone had
>>>> thought of them sooner).
>>>>
>>>>    - "Almost Ready" leads naturally into "Ready to Use" (and doesn't
>>>>    imply that a page is ever going to be "done" in the sense of couldn't still
>>>>    be better).
>>>>    - "Needs work" is much clearer than "Coming Later", especially for
>>>>    imported MSDN/MDN pages that have a lot of content on them.
>>>>
>>>> *Unless someone replies within minutes I'm going to change the names
>>>> immediately*, so that those are the values being used for the QASprint
>>>> starting today.  It'll be easier than trying to change things with a custom
>>>> script after the values have been set.
>>>>
>>>> Getting rid of the period at the end of "This article is {{State}}." is
>>>> just a simple edit of Template:Flags.  However, please warn renoirb before
>>>> you change the template, as it will trigger infinite looping updates on the
>>>> current version of Mediawiki if he's not there to make it behave.
>>>>
>>>> Finally:  When you roll out the CSS changes, can you also implement the
>>>> CSS changes for the listings tables, as described in this email:
>>>> http://lists.w3.org/Archives/Public/public-webplatform/2014Jun/0005.html
>>>>
>>>> I still hope to get a better solution for that, but for now using CSS
>>>> to convert the tables to lists will make a big improvement in readability.
>>>>
>>>> Amelia
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 12 June 2014 10:19, Jen Simmons <jen@jensimmons.com> wrote:
>>>>
>>>>> Please note I changed the names of the readiness markers.
>>>>>
>>>>> They were:
>>>>> Ready to Use
>>>>> Almost Done
>>>>> In Progress
>>>>> Coming Later
>>>>>
>>>>> I'm proposing:
>>>>> Ready to Use
>>>>> Almost Ready
>>>>> In Progress
>>>>> Needs Work
>>>>>
>>>>> I think these changes are needed to make sure this makes sense to
>>>>> people when they see only one marker, all by itself.
>>>>> "This article is Almost Ready"
>>>>> "This article Needs Work"
>>>>> etc.
>>>>>
>>>>> Coming later especially didn't really make sense when put on a single
>>>>> page. (Coming later? But it's right here, I'm looking at it...)
>>>>>
>>>>> Jen
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jun 12, 2014 at 12:09 PM, Jen Simmons <jen@jensimmons.com>
>>>>> wrote:
>>>>>
>>>>>> Here's the latest for the presentation of readiness markers:
>>>>>> http://webplatform.jensimmons.com/readiness-markers/
>>>>>>
>>>>>> Please check out the 5 page-stripes, and the revised home page.
>>>>>> And email any comments or desired changes.
>>>>>>
>>>>>> I'll wait a bit for feedback, and then let's deploy this baby first
>>>>>> thing next week!
>>>>>>
>>>>>> Jen
>>>>>>
>>>>>> Jen Simmons
>>>>>> designer, consultant and speaker
>>>>>> host of The Web Ahead
>>>>>> jensimmons.com
>>>>>> 5by5.tv/webahead
>>>>>> twitter: jensimmons <http://twitter.com/jensimmons>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>