I would suggest to use DocBook instead of HTML for documentation. DocBook is XML based format that was specifically designed for technical documentation writing. It is easy to convert to any other format that you might need, such as HTML, PDF, PostScript, text, etc.
If you would have been using DocBook, then your problem could have been easily solved. Look, for example, here (Chapter 1 of "DocBook: The Definitive Guide" by Norman Walsh and Leonard Muellner). Scroll down to "Marked sections" to see an example (specifying Draft parts of the document). You can also use the rest of the book to find a number of good reasons to use DocBook instead of HTML. :)
My 2 cents.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.