Quote:
Originally Posted by rogue_ronin
Hmmm, another thought. Does it make sense to include the following two things?
|
It does make sense, but seems a bit too detailed to me. It may be interesting, but:
- the book should never leave your computer in the intermediate stages
- after version 1.00, most of the changes will be along the lines of "fixed typo on page 123 line 15".
Quote:
|
#2: structure hints. Should someone have to examine the entire source for a clue to how it's been assembled? Or could you add something like this as a comment?:
|
Personally, I prefer the "no-clue" approach. If someone wants to see the clues, he can easily do that (for all books at one stroke) by modifying CSS, e.g.
Code:
h1.title:before { content: "Title: "; }
But once again, I must stress that I do the books for myself, to suit my needs, and not for public consumption. If you want to provide a standardized framework, the opposite approach might be better - if you use a proper tagging, hiding all "clues" would be even easier:
Code:
.clue { display: none; }