Quote:
Originally Posted by JSWolf
You have it all wrong. A template like you are suggesting is not going to help. You need to create the CSS based on what you need it to be, not what some template has for CSS.
|
Deletion. -Ed/
By template, najgori meant taking an "already working EPUB" and tweaking the innards for your own purposes... similar to how many of us here learned... by picking apart ebooks and seeing how they work.
Quote:
Originally Posted by najgori
I think it is better to start somewhere (blitz or paul salvette css framework) and learn by editing existing code.
|
Agreed... but I would avoid those two mentioned.
Quote:
Originally Posted by JSWolf
If you are going to be creating eBooks, [...] The idea is to keep it clean and simple and that requires doing ithe coding by hand. Also, clean and simple means better compatibility across a range of devices and programs.
|
Agreed, although sometimes it's best to just go back to the source document and clean it there. This will make converting and cleaning the HTML
much easier.
For a clean source document, the best thing you can do is to learn to use Styles. Here's the video I've been referencing a lot lately:
"How to REALLY use Microsoft Office: Word Styles 101". If you already know HTML+CSS, Styles are very intuitive (it's pretty much assigning classes and <span>s).
Then if you keep your book's Styles/CSS simple, you only have to do minor tweaks to handle the occasional odd/unique cases.
Like mine... I've done 550+ books, all using ~ the same CSS for 8 years.
Anyway, according to keress's initial post, they already know HTML+CSS, so all that would be needed is learning what's safe and what's not in ebooks.
