aboutsummaryrefslogtreecommitdiff
path: root/source/css (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Add a /pub/ landing pageZhiming Wang2016-07-101-0/+6
|
* Add Chinese typography featuresZhiming Wang2016-07-103-1/+80
|
* print.css: Make superscripts half size and position them correctlyZhiming Wang2016-07-101-0/+5
| | | | | Before this commit, superscripts in print adopt the sweeping body { font-size: 12px; } rule, making them too large and protruding.
* template.html: Put author and date on separate lines, and ...Zhiming Wang2016-07-101-1/+1
| | | | | | | | | | only display author when explicitly set in Pandoc metadata. Most if not all posts are by me, and there are plenty of occurrences of "Zhiming Wang" on the page. Also make authorship and date info normal instead of italic -- italic doesn't look very nice here.
* normalize.css: Update to v4.2.0Zhiming Wang2016-07-011-4/+7
| | | | https://github.com/necolas/normalize.css/releases/tag/4.2.0.
* theme.css: pre: Set overflow-x to scrollZhiming Wang2016-04-141-0/+1
| | | | | | The current behavior in Chrome and Safari is simply overflow. Not sure which commit broke it (didn't bother to bisect and regen site multiple times).
* normalize.css: Update to 4.1.1Zhiming Wang2016-04-121-49/+44
| | | | https://github.com/necolas/normalize.css/commit/39c21b3
* source/css/theme.css: Restore max-width: 100% to imgZhiming Wang2016-04-101-0/+1
| | | | Well, width restriction is still necessary...
* theme.css: Remove max-width and max-height restrictions on imgZhiming Wang2016-04-101-2/+0
| | | | | | | Sometimes I have long images, e.g., in http://zmwangx.github.io/blog/2016-04-10-emacss-got-a-redesigned-website.html, and the image would be vertically compressed in Safari. I could switch from width to max-width, but why restrict to screen height?
* normalize.css: Update to v4.0.0Zhiming Wang2016-03-201-162/+162
| | | | https://github.com/necolas/normalize.css/releases/tag/4.0.0
* source/css/theme-ultranarrow.css: Adjust index horizontal spacingZhiming Wang2016-02-011-0/+8
| | | | Horizontal space is valuable on mobile. Reduce formatting whitespace.
* theme.css: Solve image link over-wide issueZhiming Wang2016-01-301-1/+9
| | | | | | | display: block spans the entire width of the parent container. Switching to display: inline solves the problem. Fixes #11.
* source/css/theme.css: Fix printing stylesheetZhiming Wang2016-01-131-1/+5
| | | | | | | | | | | | Adjust to the right font size. Most of the heavylifting is avoided by the last commit which made all printing font sizes relative (to the base body font size). Also add "-webkit-print-color-adjust: exact" to the pre tag to hint WebKit based browsers to keep my code block background color. Nothing can be done in Firefox; users need to manually check the "Print Background Colors" advanced printing option. IE/Edge? Who knows, who cares.
* source/css/theme.css: Use relative sizes throughoutZhiming Wang2016-01-131-17/+4
| | | | | Sizes relative to the base body size are easier to update -- only need to update the base size.
* theme.css: Tweak logo text positioningZhiming Wang2016-01-091-2/+1
|
* Tweak ol and ul left padding...Zhiming Wang2016-01-081-0/+8
| | | | to left align numbers or bullets with standard paragraphs.
* Site design refresh part III: nav, i.e. logoZhiming Wang2016-01-082-24/+14
| | | | | Surprisingly, a tweaked Arial isn't so bad. Saying goodbye to Open Sans, which was tweaked to minic Helvetica Neue in the first place.
* Slightly increase h1 font sizeZhiming Wang2016-01-081-2/+2
| | | | Regular text 150% => 160%, code 22px => 23px.
* Slightly tweak icon placementZhiming Wang2016-01-081-0/+2
|
* Site design refresh part II: icon fontZhiming Wang2016-01-082-73/+27
| | | | | | | | | | | | | | | | | | | | Use slimmed icon font packaged by http://fontello.com/. I only need two glyphs: RSS and CC. I ended up picking the glyphs from the Entypo v2.0 family (https://github.com/danielbruce/entypo), licensed under SIL. I actually like the Font Awesome glyphs slightly better, but fontello currently only supports FA v4.3.0, which doesn't include the circular CC glyph I need. Old web fonts are kept for now. They will be removed after a while. See \#9. Open Sans is still in place and will be addressed later when the logo is attacked. The entire fontello package I downloaded, including the license, will be added to this repo as source/fonts/fontello/ later when I have implemented an exclude list in pyblog to prevent the directory from being copied to the deployment tree.
* Site design refresh part IZhiming Wang2016-01-082-43/+70
| | | | | | | | | | | | | | Highlights: * Change font to Times/Times New Roman + Courier; * Text slightly darkened across the board to account for the thinner Times; * Eliminate line numbers; * Use custom highlight.css (based on highlight-css supplied by Pandoc, but hightlight more classes when Pandoc falls short, e.g., span.im for Python from and import). Closes #5 because we don't have line numbers anymore.
* theme.css and template.html: Solve overflow problem in code and a tagsZhiming Wang2015-12-261-0/+5
| | | | | | | | Over-long inline <code> tag or long literal link in <a> tag used to overflow the container. This is especially bad on phones where width is very limited. This commit hopefully solves the overflow problem. Still no smarter word breaking, but it's probably just an unfortunate limitation of HTML.
* theme.css: change color of inline code to #777Zhiming Wang2015-11-261-0/+2
| | | | | | Droid Sans Mono doesn't stand out too well in a wall of PT Serif. Changing to a greyish color doesn't disrupt the black-and-white feel of the website, while giving inline code a bit more distinction.
* theme.css: deal with subpixel antialiasingZhiming Wang2015-10-101-0/+9
| | | | | | | Looks much better in desktop Safari on my non-Retina screen. Code stolen from http://www.intridea.com/blog/2014/5/8/better-font-smoothing-in-chrome-on-mac-os-x.
* template: put article-metadata in div tag instead of h2Zhiming Wang2015-09-251-0/+1
| | | | Date and author shouldn't be in the document outline.
* theme.css: fix nav icon for IE9Zhiming Wang2015-09-221-1/+1
|
* theme.css: ix problematic baseline shift of rss-icon in FirefoxZhiming Wang2015-09-051-0/+7
| | | | | Before: http://git.io/vGxpJ ; After: http://git.io/vGxpk .
* Self host webfontsZhiming Wang2015-09-052-0/+82
| | | | | Sometimes (e.g., occasionally in China) Google/FontAwesome webfonts might not be available, rendering the whole site unusable.
* Add ultranarrow theme for screens narrower than 500pxZhiming Wang2015-08-221-0/+3
| | | | Just set content width to 90% instead of 80% for narrow.
* theme.css: adjust footnote paddingZhiming Wang2015-08-221-0/+4
| | | | Make list indices roughly align with body text.
* theme.css: add 5px of vertical margins to <img>'sZhiming Wang2015-08-201-2/+1
|
* Change style of <hr> tagZhiming Wang2015-08-081-0/+6
|
* rfooter icons: switch to Font AwesomeZhiming Wang2015-08-081-21/+7
| | | | Use web font to draw icons.
* Blog icon text: switch to antialiases normal weightZhiming Wang2015-08-081-1/+3
| | | | | Open Sans Light 300 turns out to be too thin when antialiased (e.g., in mobile Safari.)
* Draw blog icon with pure HTML and CSSZhiming Wang2015-08-082-11/+27
| | | | | Using web font Open Sans (light) instead of Helvetica Neue. Text is thinner, but close enough and feels about right.
* Update print.cssZhiming Wang2015-08-051-4/+3
| | | | I forgot to update print.css to match the updated DOM last time.
* theme.css: figure caption 80% wideZhiming Wang2015-08-051-0/+2
| | | | To distinguish long captions from article paragraphs.
* update normalize.css to v3.0.3Zhiming Wang2015-08-021-11/+8
|
* rfooter icons: reduce duplication in CSSZhiming Wang2015-07-261-23/+10
|
* tons of logic and performance improvementsZhiming Wang2015-07-263-94/+86
| | | | The main aim is a more logical DOM structure and more performant CSS.
* css: replace padding with margin whenever possibleZhiming Wang2015-07-263-10/+10
| | | | Also adjusted some margins.
* adjust content width for different window widthsZhiming Wang2015-07-262-2/+6
| | | | | | | | | New: * Greater than 1440px: load theme-wide.css, content width: 50%; * Between 1024 and 1440px: standard theme.css, content width: 60%; * Lower than 1024px: load theme-narrow.css, content width: 90% (and floating nav element moves up to page top to make space).
* optimize Atom, RSS and CC icons for retina displayZhiming Wang2015-07-261-3/+6
| | | | Again using -webkit-image-set.
* narrow theme: 200x200 icon => 150x150Zhiming Wang2015-07-251-5/+6
| | | | 200x200 icon wastes too much valuable screen estate on a smart phone.
* use -webkit-image-set to make icon look sharper on Retina displaysZhiming Wang2015-07-252-0/+2
|
* select blog icon with CSSZhiming Wang2015-07-252-3/+13
| | | | | This way we can deliver the right size based on the window size (wide or narrow), rather than deliver a universal one then scale down.
* pyblog: add postprocessor process_footnote_backlinksZhiming Wang2015-07-241-0/+13
| | | | | | | | | | | | | Add class and variation selector (# U+FE0E: VARIATION SELECTOR-15) to U+21A9: LEFTWARDS ARROW WITH HOOK to fix outstanding font issue of footnote backlinks on mobile. Updated styles accordingly. Trick learned from Daring Fireball. Before: https://i.imgur.com/eUbL1k8.png After: https://i.imgur.com/msv3INn.png
* configure viewport and get rid of theme-enlarge.cssZhiming Wang2015-07-231-8/+0
| | | | | | | | | | Viewport configuration per Google's mobile usability suggestions. It not only provides a consistent experience by using device independent pixels, but also help me get rid of theme-enlarge.css, which could result in unexpectedly large font when one accidently resize to a portrait window on the desktop. Thanks Google! See https://developers.google.com/speed/docs/insights/ConfigureViewport.
* theme.css: blockquote: add bar on the leftZhiming Wang2015-07-191-1/+3
| | | | The bar is the same as that for pre. Horizontal padding reduced to 1em.
* fix line number placementZhiming Wang2015-07-173-5/+6
| | | | | | | | | | | | | | | | | Global font size in each style sheet has been tweaked very carefully so that the precise line height is very close to a whole number of pixels, so that precision alignment using em, which aligns something precise (top: 13.5em) to something inprecise (line heights, with accumulated errors due to rounding in every line), is not lost. Note that Firefox is NOT supported, since each line seems to always occupy one more pixel than the calculated line height. For some reason line numbers in the print view are still rather problematic at a page continuation. In Chrome and Safari, the first two line numbers on a new page tend to overlap, so everything afterwards are off (and on Firefox line numbers do not show up on the second page at all). Anyway, printing shouldn't be a big concern.