-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving readability for the HTML output format #9
Conversation
Update book_example/config.md
Applying Also, problems may occur with elements which you cannot break their lines. See the I take some time to think about this aspect of webdesign. My conclusion is that content readability in not linked to the global page design, at least regarding width and font-size. So I choose to set readable max-width (33em for main content, 22em for side content) independently for the containing elements. Personally, titles on the left don't bother me. Do what you think about that. But, trust me, do not try to solve typographic problems on parent of the elements where they occur. Top elements are for design. Down elements are for typography. |
Yes, directly setting it in |
Improving readability for the HTML output format
For |
Oh, yes, it makes more sense for |
Tables are always a problem for fixed width design. The best way to handle it, I think, is to apply as few rules as possible, and let the browser do its best. I know there is some scripts that propose things like "responsive tables", but I think this is out of the scope of Crowbook, at least for the moment. table{margin:auto;}
td,th{max-width:22em;}
li{max-width:33em;} Do you want me to make a pull request for that, or will you handle this update ? |
I'll handle it, I've already set it for |
I start to work on the HTML format, and I suggest some changes on the style that should improve readability. The main change is to limit the width of the
p
element to33em
so the maximum length of a line should be nearly 66 characters, which seems to be the best width for the main content of the page (don't remember exactly where I get this, may be on The Elements of Typographic Style Applied to the Web (recommended reading), but, in any case, I strongly agree).Additionally, this change avoid a annoying effect of the current design (until the window is large enough): when the menu changes state (visible or not), the vertical position of the page is moving due to the width of the content, which changes with the menu. This effect occurs in another: window resizing. With the new style, this effect is avoid until the window get too thin.
BTW: I made the change in this file as it seems to me that it's the only one used only for the HTML output. I may be wrong. Correct me if required.