Omnibus books simply need to be named properly for them to be in order. I use:
Bk1-cover
Bk1-Ch1
Bk1-Ch2
...
Bk2-cover
Bk2-Ch1
etc.
However, I don't like putting more than 3-4 books in the same file depending on the length of each book. It could make the file size too large which could have adverse effects on older devices.
It is simple to make books appear the same way. Just use the same css stylesheet on all the books. Once you have created your css the way you want it, you can right click and Save As. Then in the other books you can import the same css file....don't forget to link each html file to your new css file.
The HTML files should be kept VERY CLEAN with minimal classes (only those that are necessary) and (try really hard for)
zero inline styles.
Sorta like this:
Code:
<body>
<h2>Chapter Title</h2>
<p class="first">First paragraph</p>
<p>2nd para</p>
<p>3rd para</p>
<p class="SecBrk">Scene break paragraph</p>
<p>Next para with <em>a phrase emphasized in italic</em></p>
</body>
css:
h2 {text-indent:0; text-align:center; margin:1em auto;
font-style:bold; font-size:1.3em; font-family:serif}
p {text-align:left; text-indent:1.2em; margin:0}
p.first {text-indent:0}
p.SecBrk {text-indent:0; margin-top:2em}
em {font-style:italic}
(obviously adjust the css to your taste)
I think it is pretty silly to put a class on every paragraph just to assign the default class such as:
Code:
<p class="para">One of 5000+ paragraphs</p>
css:
p.para {text-align:left; text-indent:1.2em; margin:0}
Save class assignments for elements that are NOT the default style. That keeps things clean and saves the device/app from having to decode unnecessary styling.
If you consistently use simple html coding then using the same css file will make all the books look similar.
I hope that helps!
Cheers,