This would be a testcase for testing mozilla.org style sheets. It's not a very inspiring document, but you might find it useful as an example of what you can do with the predefined markup classes. If you're using Mozilla, you might find the View Selection Source context menu item useful.
Paragraph text.
Paragraph text.
Paragraph text.
Paragraph text.
Paragraph text.
dl
-style TOC [toc]An overview of how to get the source, develop patches, get them reviewed, super-reviewed and checked in the tree.
How is the source code organized, where to start, critical tools, rules to follow to contribute.
What code needs super-review, what to do if you're seeking a super-review, a list of super-reviewers, plus some tips about what to consider in your code before seeking super-review.
Paragraph Text [para] Please note that this is a note. [note] A paragraph containing block level content follows ([para]):
When writing technical documentation, especially online documentation, strict organization assumes a particularly important role. The reader is often there only to find some specific piece of information, and typically scans rather than peruses the text. To make this easier,
You want the main points of your writing to stick out so that the reader can find the right section quickly and easily. Snag them first, then explain.
Paragraph Text
A block-level note. A block-level note. A block-level note. A block-level note. A block-level note. A block-level note. A block-level note. A block-level note. A block-level note. A block-level note.
Going down another level...
Normally important notices aren't put in sub-subsections, but we're going to make an exception and put one right here:
This is a very important paragraph [important] with emphasized text [em], strongly emphasized text [strong], even stronger [stronger], very-strong emphasis [very-strong]. Right, so, don't cross-post, what.
Adding another one for good measure.
This is a normal paragraph with emphasized text [em], strongly emphasized text [strong], even stronger [stronger], very-strong emphasis [very-strong].
And, of course, don't forget to brush your teeth [important], for the wrath of the dentist can be frightening indeed.
Let's learn about coding! Here's an example [example]:
//comment [remark] variable [var] = new Type; variable [var] = some - value; [strong]
As you see, it's possible to do syntax highlighting. As you can also see, emphasis in code blocks [codeblock] can be useful for pointing out stupid things. (Or good things, if you prefer.) The code for the above is
<pre class="code"> <span class="remark">//comment</span> <var>variable</var> = new Type; <strong><var>variable</var> = some - value;</strong> </pre>
Of course, we might just want to forgo the syntax highlighting and write
<pre class="code"> <span class="remark">//comment</span> <var>variable</var> = new Type; <strong><var>variable</var> = some - value;</strong> </pre>
which is much easier to type.
This is a code block with emphasized text [em] ; variable ;markup
, strongly emphasized text [strong] ; variable ;markup
, [some random code] even stronger [stronger] ; variable ;markup
, [some random code] very-strong emphasis [very-strong] ; variable ;markup
. Highest level [lineannotation] [more code] important [important] ; variable ;markup
. [more code again]
The following is an incorrect example.
//comment [remark] variable [var] = new Type; variable [var] = some - value; [strong]
Losing the pointer to the new Type creates a memory leak.
the following is an incorrect block of code.
//comment [remark] variable [var] = new Type; variable [var] = some - value; [strong]
It's often useful to present screenshots when talking about a graphical user interface. Here's one [screenshot] of the Phoenity Theme for The Browser Formerly Known as Phoenix:
Of course, not all diagrams are screenshots. This one [figure] diagrams CSS3 glyph-orientation [code]
as it worked in the February 26th CSS3 Text Working Draft [ex-ref]
which, as you can see, was a mess.
Some inline sample output [samp], user input [kbd], command filename [var] > test.out [command]
A snippet from Bernd's debugging table reflow doc, demonstrating a computer output block [screen] and callouts:
AssignNonPctColWidths en [co] max=4500 count=0 ***START TABLE DUMP*** mColWidths=-1 -1 -1 -1 col frame cache -> 0=00B93138 1=00B931F0 2=024DD728 3=024DD780 **START COL DUMP** colIndex=0 isAnonymous=0 constraint=0 widths=-1 -1 -1 -1 -1 -1 -1 -1 -1 -1 **END COL DUMP** **START COL DUMP** colIndex=1 isAnonymous=0 constraint=0 widths=-1 -1 -1 -1 -1 -1 -1 -1 -1 -1 **END COL DUMP** **START COL DUMP** colIndex=2 isAnonymous=0 constraint=0 widths=-1 -1 -1 -1 -1 -1 -1 -1 -1 -1 **END COL DUMP** **START COL DUMP** colIndex=3 isAnonymous=0 constraint=0 widths=-1 -1 -1 -1 -1 -1 -1 -1 -1 -1 **END COL DUMP** ***END TABLE DUMP***
The en [callout] stands for entrance (ex for leaving a routine). The first line of the data dump shows that no width has yet...
In time for the mozilla1.4b [productnumber] (Mozilla 1.4 Beta) release, Hacking in a Nutshell has finally been moved to /hacking/index.html [filename].
ol[code]
-style task listdl[code]
-style task list("Back to top" links are [back])
A layout engine is...
Back to topHeader 1 | Header 2 |
---|---|
odd 1 | odd 2 |
even 1 | even 2 |
regular 1 | regular 2 |