{"id":2930,"date":"2013-08-30T17:12:26","date_gmt":"2013-08-30T23:12:26","guid":{"rendered":"http:\/\/bililite.com\/blog\/?p=2930"},"modified":"2013-08-30T17:12:26","modified_gmt":"2013-08-30T23:12:26","slug":"writing-and-the-web","status":"publish","type":"post","link":"https:\/\/bililite.com\/blog\/2013\/08\/30\/writing-and-the-web\/","title":{"rendered":"Writing and the Web"},"content":{"rendered":"

I haven't been blogging or programming a whole lot over the past year, since I started teaching two Tanach (Bible) classes. Even two hours a week, irregularly, represents a lot<\/em> of work, and pretty much has sucked up all my intellectual free time. So not much Javascript. But I have been recording the notes (sort of condensed essays, 1000–2000 words) online so I could refer to them, and I've learned something about creating a website that is text, not data or doing-stuff, oriented. The site is kavanot.me<\/a>; the classes are Shiurim<\/a> and Parasha<\/a>.<\/p>\r\n\r\n

I don't expect any reader of this blog to understand the Hebrew or the details of Biblical exegesis, but these notes are more about design issues and resources that would be relevant to almost anyone.<\/p>\r\n\r\n\r\n

Structure<\/h3>\r\n

HTML5 makes the basic structure easy:<\/p>\r\n

<body>\r\n  <header>\r\n    <h1><\/h1>\r\n    <nav><\/nav>\r\n  <\/header>\r\n  <article>\r\n    <section><\/section>\r\n  <article>\r\n  <footer>\r\n  <\/footer>\r\n<\/body><\/code><\/pre>\r\n
I'm not a believer in side bars (unless I can get some money out of advertising!)<\/p>\r\n\r\n\r\n
Words<\/h3>\r\n
People have been printing books for 500 years, and lots of rules and traditions have developed. Treat them like rules of grammar: you can violate them, but violate them intentionally, not out of ignorance. My source for those rules is Matthew Butterick<\/a>, especially his summary<\/a> (and it's worth paying for the book<\/a>).\r\n
As he points out, websites tend to try to be efficient and cram as many letters into as little space as possible, which makes no sense (people do know how to scroll) and just makes the text hard to read.<\/p>\r\n
So my CSS follows (the source file is kavanot.me\/css\/stye.scss<\/a>). I use SCSS<\/a> (actually scssphp<\/a>) so I can use variables and calculations; I can't imagine going without it now.<\/p>\r\n\r\n
Point Size<\/h4>\r\n
Butterick recommends 15-25 pixels for the font size; I use 
$fontsize: 18px;\r\nbody { font-size: $fontsize; }\r\nheader { font-size: 120%; } \/* 21.5px *\/\r\nnav {font-size: 85%; } \/* 15px *\/\r\nfooter { font-size: 75%; } \/* 13.5px; this is a little small but seems appropriate\r\n                             for the \"fine print\" part of the site *\/<\/code><\/pre>\r\n\r\n
Line Spacing<\/h4>\r\n
Butterick recommends 120-145% of the point size. I use<\/p>\r\n
$linespacing: 1.35;\r\nbody, h1, h2, h3, h4 { line-height: $linespacing; }\r\n\/* Need to set the line height for each header since they have different\r\n   font sizes and the line spacing has to be proportionate *\/<\/code><\/pre>\r\n\r\n
Line Length<\/h4>\r\n
This was the hardest for me to acknowledge, but long lines make for hard-to-read text. Lines should be 45-90 characters long. That's less than 650 pixels for 18px type. It makes for lots of whitespace around the text; if I want my \"page\" to be 850px, I use:<\/p>\r\n
$linewidth: $fontsize * 35; \/* found empirically *\/\r\n$width: 850px;\r\n$linepadding:($width - $linewidth) \/ 2;\r\narticle { width: $width; }\r\nsection { padding: 0 $linepadding; }<\/code><\/pre>\r\n
Note that since the standard box model<\/a> calculates the width without including the padding, we set the padding on the child of the <article><\/code>.<\/p>\r\n\r\n
Fonts<\/h4>\r\n
Butterick advises against \"goofy\" fonts, though I couldn't resist and used 1543 Humane Jenson<\/a> (licensed for non-commericial use) for the \"display\" font (for headers). He also advises against using common fonts for esthetic reasons; you want your text to stand out. I'm not a typography guru and really couldn't tell the difference. I would have no problems with font-family: sans-serif<\/code> and living with whatever your browser came up with.<\/p>\r\n
But I need fonts with the full gamut of Hebrew glyphs, including properly placed diacritics. The only choices are those listed by Mechon Mamre<\/a>, and I think the nicest by far is the SBL Hebrew<\/a> font, with nice English glyphs as well, and very legible on screen and on paper.<\/p>\r\n
To generate webfonts, I use FontSquirrel<\/a>. But there are a few caveats. You have to select the Expert mode and select No Subsetting (or Custom Subsetting if you really want to limit the glyphs) to get all the foreign language glyphs. For the professional fonts with their own TrueType hinting, make sure to keep it (don't use the Font Squirrel hinting; it messed up the Hebrew badly).<\/p>\r\n\r\n
Curly Quotes<\/h4>\r\n
I know I should use real quotes and apostrophes (“ ” ’<\/span>) rather than the typewriter straight ones (\" '), but who wants to keep typing &ldquo;&rdquo; all the time? I could use a PHP version of Markdown<\/a>\r\nbut I decided it would be more educational to write my own; I don't mind writing out straight HTML for most of the formatting.<\/p>\r\n
The only trick is that you don't want to convert quotes inside<\/em> tags: <a href=\"http:\/\/example.com\"><\/span> should not become\r\n<a href=“http:\/\/example.com”><\/span>. But I solved that problem<\/a> already. So all I need is this on the server side:<\/p>\r\n
$text = preg_replace_text ('\/\"(.+?)\"\/', '“$1”', $text);\r\n$text = preg_replace_text ('\/\\'(.+?)\\'(\\W)\/', '‘$1’$2', $text);\r\n$text = preg_replace_text ('\/\\'(\\w)\/', '’$1', $text);\r\n$text = preg_replace_text ('\/\\.\\.\\.\/', '…', $text);\r\n$text = preg_replace_text ('\/--\/', '—', $text);<\/code><\/pre>\r\n
to handle curly quotes, apostrophes, ellipses and em-dashes. It's not perfect; if the quote contains tags it will fail, and the quotes come out the wrong way for Hebrew, but those are rare and I can hand-correct them.<\/p>\r\n\r\n
Paragraphs<\/h4>\r\n
Butterick recommends 1–4 ems of space for first-line indents, or 4–10 points between paragraphs. I go for the latter: p { margin-bottom: 5px; }<\/code>.<\/p>\r\n\r\n\r\n
Design<\/h3>\r\n
All websites look the same, if you stand far away. Butterick has an essay<\/a> decrying that, saying we need better, more innovative design. But he contradicts himself: all books look the same as well, if you stand far enough away. He argues that 500 years of print design experience have led to a set of common standards; I think 20 years of web design, while not quite 500 years,  has led to a set of common standards that everyone expects when reading. When you see a site with a big graphic header, tabs\/navigation bar under that, real text and pictures in the middle, ads and some more navigation on one or both sides, and fine print and fine navigation after scrolling all the way down, you're home. You know what to do, what to look for. Butterick has a lovely site<\/a> for his Concourse font but it's unreadable; you can edit the type samples and download a PDF specimen file but that information is lost among all the pretty examples.<\/p>\r\n
Enough screed. I want my site design to get out of the way; kavanot.me<\/a> is probably less minimalist than I would create now but I've grown to like it. I need five colors: the main text contrasting with the background (a pale neutral) and another color for display text. I want a fixed page width (as above, 850px seems to work well) so I need an unobtrusive deep background color for the page outside that. And some kind of border\/shadow between the page and the deep background.<\/p>\r\n
I have no design or color sense, so I browse colourlovers.com<\/a> palettes (which conveniently have five colors each) until I find something I like; kavanot.me uses Published in 1932<\/a>.<\/p>\r\n
So the CSS is:<\/p>\r\n
body {\r\n  background-color: $deepbackgroundcolor;\r\n}\r\nheader {\r\n  color: $displaycolor;\r\n}\r\narticle {\r\n  background-color: $backgroundcolor;\r\n  color: $textcolor;\r\n}<\/code><\/pre>\r\n
Prior to CSS3, I would have use images created in Photoshop for a soft border; something like top.png<\/code>: \"header, middle.png<\/code>: \"article and bottom.png<\/code>: \"footer, with CSS like:<\/p>\r\n
header {\r\n  background: url('\/images\/top.png') no-repeat bottom;\r\n}\r\narticle {\r\n  background: url('\/images\/middle.png') repeat-y center;\r\n}\r\nfooter {\r\n  background: url('\/images\/bottom.png') no-repeat top;\r\n}<\/code><\/pre>\r\n\r\n
But now I can use the incredibly complicated box-shadow<\/code><\/a> to create the border. box-shadow allows you to build up multiple shadows, so I can use a centered external shadow and an inset one. A straight centered shadow (box-shadow: 0 0;<\/code>) would be hidden behind the element, so you have to use the spread value to make the shadow bigger, then adjust the blur to smooth out the edge into the deep background. I used:<\/p>\r\n
article {\r\n  box-shadow: \r\n    inset 0px 0px 30px 30px $bordercolor, \/* fade on the inside *\/\r\n    0px 0px 10px 10px $bordercolor; \/* fade on the outside *\/\r\n  ;\r\n}<\/code><\/pre>\r\n
And that gives me my subtle border with no images, easy-to-modify CSS, and degrades cleanly for browsers that don't support box-shadow<\/code>.<\/p>\r\n\r\n
More thoughts on web design as I get around to documenting them.<\/p>","protected":false},"excerpt":{"rendered":"I haven't been blogging or programming a whole lot over the past year, since I started teaching two Tanach (Bible) classes. Even two hours a week, irregularly, represents a lot of work, and pretty much has sucked up all my intellectual free time. So not much Javascript. But I have been recording the notes (sort […]","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"_links":{"self":[{"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/posts\/2930"}],"collection":[{"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/comments?post=2930"}],"version-history":[{"count":28,"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/posts\/2930\/revisions"}],"predecessor-version":[{"id":2960,"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/posts\/2930\/revisions\/2960"}],"wp:attachment":[{"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/media?parent=2930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/categories?post=2930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bililite.com\/blog\/wp-json\/wp\/v2\/tags?post=2930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}