CSS Foo Module Level N

Shortname: css-foo
Level: 1
Status: ED
Group: csswg
TR: http://www.w3.org/TR/css-foo/
ED: http://dev.w3.org/csswg/css-foo/
Editor: Name1, Company1, http://example.com/contact
Editor: Name2, Company2, name2@example.com
Abstract: This module introduces the 'foo' property and related values, which do bar and baz.
Ignored Terms: div, dl, dfn

Introduction

This section is not normative. Provide background, motivation, etc.

Sample section

Look at the mark-up in this section for examples. See the documentation for more precise instructions. The companion of this template shows the processed result. To refer to HTML, use [[HTML40]] (note the double square brackets). To make a normative reference, insert a “!”, like this: [[!CSS3SYN]] The currently available list of bibliographic data can of course be extended. We write about a property such as 'foo' like this and about a piece of CSS code like this: ''foo: bar''. (Note that if it looks like a "property: value", it'll automatically link to the property.) Inline HTML and XML are similar, but use the CODE element: <blockquote>...</blockquote> and <r:xyz>...</r:xyz>. Note: Note that the property will automatically be linked to its definition. To define terms into the index, there are many variants, but hopefully the simplest will be the most common. Note: Note that you can add non-normative notes like this. Of course, multi-paragraph notes are also possible: just enclose them in a div:
Note that this note is a multi-paragraph note. It doesn't need to have two paragraphs, but it could.
Displayed examples come in eight different types: CSS examples that need no separate paragraph of explanation are put in a simple PRE: 
		EM { font-style: italic }
CSS examples that need extra text need a DIV.
The following example is the same as the previous one, but now it is explained: 
EM { font-style: italic }
Illegal CSS examples (examples of errors) are the same, but with class "illegal example". Examples of HTML and XML code have class "html" and "xml"respectively, but are otherwise ditto. A formal definition of a property looks like this:

Internal display model: the 'display-inside' property

		Name: foo
		Value: inline-inside | block-inside | table | ruby | icon
		Initial: text
		Applies to: all elements
		Inherited: no
		Percentages: n/a
		Media: visual
		Computed value: specified value
		Animatable: no
		Canonical order: per grammar
value-name
Define values using a dl. Note that the dl wrapper specifies the default dfn type and what property it's for, so you don't have to repeat that information in each individual definition.
Cross-references are created by enclosing a term or phrase in <dfn> (like the word cross-references earlier in this sentence). Then an <a> without an href='' attribute with the same text content will automatically be linked. Both <dfn>s and <a>s are typed, which allows the same text to appear as different types of terms without a collision. The type can often be inferred, but sometimes it needs to be specified, like when you're linking to a Foo WebIDL interface. And a figure with a caption is done like this:
A table with a caption above it; both have margins and the margins between them are collapsed, as is normal for vertical margins.
Just a random image. Use SVG if you can. Otherwise, W3C prefers PNG over GIF (obviously, since PNG is a W3C Rec).
Don't forget to write the alt.

An open issue or editorial remark is OK in a WD, but they should be resolved/removed before the document goes to “CR” (Candidate Recommendation). Use class=“issue”.

Inline issues will be copied into an Issues Index at the end of the document, for easy reference. 

		/* Write WebIDL in a <pre class="idl"> as plain text. */
		interface Foo {
			readonly attribute DOMString bar;
			boolean baz(FooDict Arg1, (DOMString or Foo) Arg2);
		};

		dictionary FooDict {
			sequence<Foo> foo;
			boolean bar;
			DOMString baz = "qux";
		};