Intended audience: users, XHTML/HTML coders (using editors or scripting), script developers (PHP, JSP, etc.), CSS coders, schema developers (DTDs, XML Schema, RelaxNG, etc.), XSLT developers, Web project managers, and anyone who is new to internationalization and needs guidance on topics to consider and ways to get into the material on the site. xxx adapt this to describe the intended reader of the article.
When is it appropriate, or not, to use language negotiation?
This text should be kept as short as possible. It gives background information, such as what is the problem, and says what the article will do. If you need a longer introduction, use a subsection with the title 'Background".
All the text in this div will be displayed to the right of the main text flow, but will displace the right side of the main text flow if there is another floated item to its right. It was designed to be used at the top of a page where sidenotes may overlap with stuff at the top of the right page column. Normally you should use a regular sideinfonote, illustrated below.
This section has a standardised heading and should give the answer as briefly as possible, for those who just need a reminder or a few pointers.
When providing additional paragraphs in the answer, try to use one paragaph per point, and summarise that point in the first sentence of the paragraph. This helps people skim the article for relevant information.
The answer should be written in an easy to read style, but be as direct and simple as possible. You should also take great pains to ensure that the answer remains very focused on just directly answering the question at the beginning of the FAQ. Put tangential information in the 'by the way' section or in a different article. Of course, a similar simplicity and directness should be used for general articles, too.
This section has a standardised heading and can be used to treat the answer in more depth, for those who need it.
Try to use short, task- or question-oriented subsections to make it easier for readers to find the specific information they are looking for.
Here's a section that uses level 4 headings.
Some text inside a level 4 heading.
This section has a standardised heading and is for information that readers don't normally need to know, but that is available if needed. For example, how to work with legacy character encodings (given that everyone should just use UTF-8). Again, use subsections to modularise and signpost the topics.
This section illustrates a number of non-phrasal elements that you might want to use in your article.
Lead in. A lead in will be bolded text at the start of a paragraph. It should be used to break up long passages for the reader, so that they can read more comfortably, and also find specific information quickly on review.
SIDE NOTE Information at the beginning of this div with class="sidenoteGroup" is just part of the ordinary flow of the article. The div, however, marks the point at which any associated note text will occur in a voice browser or destyled page.
You can have as much content as you like here, using p, table, div or any other markup.
This text is a note related to the text enclosed in the div with class="sidenoteGroup". It will normally be displayed in the right column of the page, and will start level with the start of the aformentioned text (ie. the text at the beginning of the div with class="sidenoteGroup".
You can put any markup you like in here, and you should use a p or div tag with class="info" or class="warning" on the first one, to produce the dropcap style indicator of what type of note this is.
Inline markup conventions are given in the style guide.