aboutsummaryrefslogtreecommitdiff
path: root/source (follow)
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* 20150805 Switching to capitalized commit messagesZhiming Wang2015-08-051-0/+14
|
* 20150805 Should Apple split up iTunes on OS X?Zhiming Wang2015-08-052-0/+22
|
* theme.css: figure caption 80% wideZhiming Wang2015-08-051-0/+2
| | | | To distinguish long captions from article paragraphs.
* latest post: add a TL;DR, pointing to zmwangx/safari-sync-chrome-bookmarksZhiming Wang2015-08-021-0/+4
|
* 20150802 Sync Chrome bookmarks with Safari on OS XZhiming Wang2015-08-022-0/+60
|
* update normalize.css to v3.0.3Zhiming Wang2015-08-021-11/+8
|
* latest post: fix typoZhiming Wang2015-08-011-1/+1
|
* latest post: another minor updateZhiming Wang2015-07-311-1/+1
|
* latest post: minor updateZhiming Wang2015-07-311-1/+1
|
* 20150730 The sad state of Finder on El CapitanZhiming Wang2015-07-301-0/+45
|
* 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-2610-9/+12
| | | | Again using -webkit-image-set.
* optimize a few images that I forgot to optimize beforeZhiming Wang2015-07-263-0/+0
|
* narrow theme: 200x200 icon => 150x150Zhiming Wang2015-07-254-6/+7
| | | | 200x200 icon wastes too much valuable screen estate on a smart phone.
* regen icon imagesZhiming Wang2015-07-257-0/+0
| | | | icon.tex was modified in bbaf880.
* 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.
* 20150725 dl? cmplnts?'s web doesn't suckZhiming Wang2015-07-253-0/+16
|
* create 200x200 icon, and use it on every pageZhiming Wang2015-07-252-1/+1
| | | | | 400x400 is a waste, given that the size of the logo set by CSS is either 100x100 (wide) or 200x200 (narrow).
* create separate square icon as Apple touch iconZhiming Wang2015-07-254-3/+24
| | | | | | Round icon with transparent filling doesn't work well on iOS's home screen, because the transparent part will be filled in black. Also, the letters ZW have been enlarged to look better in a square icon.
* 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
* English improvementsZhiming Wang2015-07-231-2/+2
| | | | Yay.
* 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.
* add keybase proof to .well-known/keybase.txtZhiming Wang2015-07-221-0/+76
|
* latest post: replace \pi by Unicode πZhiming Wang2015-07-191-1/+1
| | | | \pi is eaten by Pandoc.
* combine broken blockquotesZhiming Wang2015-07-191-10/+10
| | | | | Add a `>` between paragraphs so that a multi-paragraph block quote is inside one <blockquote> tag. Otherwise the left bar would be broken.
* 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.
* 20150719 GitHub experimental attachment formats: PDF, DOCX and PPTX!?!Zhiming Wang2015-07-192-0/+86
|
* index.md: add Keybase linkZhiming Wang2015-07-191-1/+1
|
* 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.
* add print stylesheetZhiming Wang2015-07-171-0/+15
|
* narrow theme: add 10% padding at article bottomZhiming Wang2015-07-171-1/+1
|
* design mobile and narrow window friendly themeZhiming Wang2015-07-173-18/+74
| | | | Tested on iPhone 6 Plus (both portrait and landscape).
* index.html TOC: use <table> instead of <ul>Zhiming Wang2015-07-171-5/+7
| | | | | | | | | | | | For better formatting. The following screenshots illustrate the difference: * https://i.imgur.com/ZfkUpBG.png * https://i.imgur.com/S6cRK00.png I also reduced the indentation on the left of each year's index from 2em to 1em.
* 20150715 Zsh: save stdout, stderr, and return value of command to different ↵Zhiming Wang2015-07-151-0/+33
| | | | variables (without temp file)
* index.md: add no-SNS declarationZhiming Wang2015-07-121-1/+1
|
* dl? cmplnts? in Apple News: update with new screenshotZhiming Wang2015-06-302-0/+6
|
* 20150629 dl? cmplnts? in Apple NewsZhiming Wang2015-06-292-0/+20
|
* 20150627 Automatically clean up "Previous Mobile Applications"Zhiming Wang2015-06-271-0/+122
|
* 20150626 iOS 9: searchable SettingsZhiming Wang2015-06-273-0/+14
| | | | | Also update previous post 2015-05-06-searchable-settings-are-one-honking-great-idea-lets-do-more-of-those.md.
* 20150623 All problems solved!?Zhiming Wang2015-06-231-0/+28
|
* theme.css: shrink paragraph spacing in and between footnotesZhiming Wang2015-06-161-0/+4
|
* fix font issues: moving back to Droid Sans Mono for codeZhiming Wang2015-06-162-2/+12
| | | | | | | | | | | | | | | | | I just noticed that code font is crazy without Consolas installed (I recently reinstalled my OS and got rid of Office for Mac 2011 — that's probably why). The line numbers are all off (since the line heights are carefully pre-calculated, and fallback fonts of different leadings won't help). Therefore, I'm moving to the quite nice looking and controllable Droid Sans Mono. Isn't as satisfactory as Consolas on the web, but certainly better than Monaco. Note: I originally copied my list Consolas, Monaco, 'Andale Mono', monospace (I added Courier since I like it a lot as the primitive monospace font) from MDN Wiki, but now it looks like a bad choice when I don't have Consolas any more. By the way, MDN Wiki renders line numbers using JS, so at least they are able to calculate the line heights. I'm serving everything statically, so this is a problem.
* 20150612 The tip of the icebergZhiming Wang2015-06-122-1/+23
|
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-16 00:40:05 +0000