W3C home > Mailing lists > Public > public-webplatform@w3.org > January 2013

Re: CSS Property Milestone Project Plan

From: Mike Sierra <letmespellitoutforyou@gmail.com>
Date: Thu, 10 Jan 2013 13:12:52 -0500
Message-ID: <CAECD2431vYCM_7jbf=ezN3OaD82E=_4ULUGcEX0znB48kJ2Z=w@mail.gmail.com>
To: Chris Mills <cmills@opera.com>
Cc: Julee Burdekin <jburdeki@adobe.com>, Alex Komoroske <komoroske@google.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Yes, I was referring to all the implemented properties.  I expect the
CSS3 would be far more popular search topics, not the older core
properties, but I appreciate the reasoning of starting with the
latter.  Perhaps it would be useful to add a CSS version flag for the
criteria Chris mentions, with which to present a more manageable set
of tables on the css/properties page.

--Mike S

On Thu, Jan 10, 2013 at 11:11 AM, Chris Mills <cmills@opera.com> wrote:
> Do you think Mike was referring to all the CSS properties, including all the proprietary non-standard browser stuff? That shouldn't be a part of the central task.
> Also, I could imagine the number being far higher than 80, if we choose to include all the properties from the nascent CSS3 modules, as well as the completed stuff.
> I think we need to think about how we are going to do this. Should we tackle it in subsets, with different prioriites? For example
> * Set 1: Everything defined in CSS 1/2.x
> * Set 2: All CSS3 stuff that has at least two stable implentations
> * Set 3: All CSS3 stuff that is a bit further off
> * Set 4: All non standard CSS
> ?
> Chris Mills
> Opera Software, dev.opera.com
> W3C Fellow, web education and webplatform.org
> Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)
> On 10 Jan 2013, at 15:55, Julee Burdekin <jburdeki@adobe.com> wrote:
>> Hi, Alex:
>> This is exciting! A few minor things:
>>        Do we have a date for this milestone?
>>        Mike Sierra mentioned to me there are over 256 CSS properties, compiled from various browsers' lists of computed styles. So can you provide a clear criteria for what you're including in your list of ~80 CSS properties? Just a quick sentence about how you chose what you chose.
>>        Can we say each page goes through at least one round of writing/tech review/copy editing?
>>        A nice-to-have: in addition to the "representative property", a quick checklist for the writer to go through to ensure completion/conformity to ideal? (What makes it the property we chose to be representative?)
>> Regards.
>> J
>> ----------------------------
>> julee@adobe.com
>> @adobejulee
>> From: Alex Komoroske <komoroske@google.com>
>> Date: Wednesday, January 9, 2013 6:20 PM
>> To: "public-webplatform@w3.org" <public-webplatform@w3.org>
>> Subject: CSS Property Milestone Project Plan
>> Resent-From: <public-webplatform@w3.org>
>> Resent-Date: Wednesday, January 9, 2013 6:21 PM
>> Hi all,
>> As discussed on the call on Tuesday, I propose that our first milestone be focused on making our CSS property pages in particular the best on the web.
>> I've outline the high-level plan (including rationale) at http://docs.webplatform.org/wiki/WPD:Tasks/CSS_Property_Milestone .
>> Please take a look and let me know what you think. On Friday I will begin enumerating the pages and start looking for the good representative article to help us set our guidelines.
>> --Alex
Received on Thursday, 10 January 2013 18:13:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:46 UTC