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

Re: Guide to implementing CSS property pages

From: Chris Mills <cmills@opera.com>
Date: Tue, 29 Jan 2013 10:26:55 +0000
Cc: PhistucK <phistuck@gmail.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Message-Id: <7798AE7C-AAF8-4FA3-B0E0-094F5150C2BF@opera.com>
To: Mike Sierra <letmespellitoutforyou@gmail.com>
All sounds sensible Mike - some great groundwork done here.

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 28 Jan 2013, at 22:24, Mike Sierra <letmespellitoutforyou@gmail.com> wrote:

> FYI, I went ahead and punched a bunch of content into the css/units
> space, which could probably use another category on the top-level CSS
> page. I decided not to create a million picayune pages for each
> individual unit, so I sliced them up into broad categories.  Also
> decided to cover various reba() & hsla() values under that tree rather
> than under css/functions, where I thought they'd be hard to relate to
> each other. And I'm afraid I used the "concepts" template, which may
> have been inappropriate.  It's all pretty skeletal & straight out of
> the spec, so it could use more in the way of examples & other
> improvements.
> --Mike Sierra
> On Mon, Jan 28, 2013 at 11:44 AM, Mike Sierra
> <letmespellitoutforyou@gmail.com> wrote:
>> On Mon, Jan 28, 2013 at 10:09 AM, Chris Mills <cmills@opera.com> wrote:
>>> Thanks for the comments guys!
>>> I have answered pretty much all of Mike's comments. I also agreed entirely with PhistucK's comments, and have implemented a page about CSS images at http://docs.webplatform.org/wiki/concepts/css-images and referenced it from my CSS property guide (http://docs.webplatform.org/wiki/WPD:CSS_property_guide). It makes a lot of sense to cover concepts and other info that applies to several properties, in separate pages.
>> That point is worth stressing as part of the instructions. Authors
>> should ask whether information they want to include for this property
>> is also appropriate for other properties as well. In that case, link
>> to it elsewhere.  In general, draw links within the site, even to
>> appropriate destinations that don't exist yet.  In this case, url()
>> and various *-gradient() functions are viable targets within the
>> "css/functions" tree. (Either search or navigate to css/functions to
>> research existing pages.) Or if you're describing background colors,
>> rather than detail how RGBA/HSLA values work, you should point to
>> css/units (caveat: that tree doesn't exist yet). If you find yourself
>> using any other common jargon that's hard to classify & that readers
>> might not be familiar with, create a link within the top-level
>> "concepts" tree, e.g., "viewport," "vendor prefixes," or "standards
>> mode." Readers may also benefit from links to tutorials on the subject
>> available as "CSS learning material." (Other areas such as HTML,
>> Javascript, and SVG have their own learning-material areas.)
>> --Mike Sierra
Received on Tuesday, 29 January 2013 10:27:27 UTC

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