Re: Guide to implementing CSS property pages

Again FYI, the font-size page (the live one, not the mockup) is now
modified to link to css/units/length, for anyone using that page for

I also got tired of looking at those unresolved css/concept links in
the overview table, so I added a bit of text there as well.  This
might have been discussed before, but I'm unclear if we're going to
support both "concept" and "glossary" categories, and if so what's the
distinction. (The stuff I just punched in is very short and
glossary-like, while a lot of "concept" pages are more like
tutorials.)  There is a whole lot of content under glossary/main that
points to random top-level pages. & I don't mean for this to be a
distraction, btw, just pointing out issues where I find them.

--Mike S

On Tue, Jan 29, 2013 at 5:26 AM, Chris Mills <> wrote:
> All sounds sensible Mike - some great groundwork done here.
> Chris Mills
> Opera Software,
> W3C Fellow, web education and
> Author of "Practical CSS3: Develop and Design" (
> On 28 Jan 2013, at 22:24, Mike Sierra <> 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
>> <> wrote:
>>> On Mon, Jan 28, 2013 at 10:09 AM, Chris Mills <> 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 and referenced it from my 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 16:17:33 UTC