Philosophy Guide to creating HTML versions
Jump to navigation Jump to search
- If the PM has requested an HTML version of the text, you should see if there are any special requirements, such as the stylesheets for Punch.
<h1></h1>tag in HTML should be used for the title of the work.
<h2></h2>tag in HTML should usually be used for the chapter titles.
- Paragraphs should be enclosed in
<p></p>tags. Make sure that every paragraph has both a start and end tag.
<br>element should be used to force line breaks only when necessary. The form with the closing slash is used in XHTML (GuiGuts default); the form without the slash is used in HTML.
<hr>element should be used sparingly as a thought break.
- There is some debate about the best way to represent poetry and tables.
- Presentational attributes, other than bold and italic, should use CSS to produce the correct rendering.
- No bare text. There should be no content of the work that is not wrapped in some sort of HTML markup. Every paragraph, line, poem, header or other entity should be marked up.
- Easy Epub describes some simple checks and edits to ensure your book will look good on e-readers.
- PP examples on PG lists some amazing and beautiful works.
- Tools for Creating HTML versions points to software tools.
- HTML advice threads discussions in the forums.
- CSS Cookbook explores some of the many ways to handle the parts of an etext, including the ToC, the index, illustrations, footnotes, sidenotes, drama (?link?) and poetry.