| Commit message (Collapse) | Author | Files | Lines |
|
Date and author shouldn't be in the document outline.
|
|
Will write a short blog post about this decision soon.
|
|
Looks slightly more professional.
|
|
Sometimes (e.g., occasionally in China) Google/FontAwesome webfonts
might not be available, rendering the whole site unusable.
|
|
Just set content width to 90% instead of 80% for narrow.
|
|
I accidentally removed syntax highlighting in 94f82685672bcd4e5731de3c1c61e79f7edc07b2.
|
|
Use web font to draw icons.
|
|
Open Sans Light 300 turns out to be too thin when antialiased (e.g., in
mobile Safari.)
|
|
Using web font Open Sans (light) instead of Helvetica Neue. Text is
thinner, but close enough and feels about right.
|
|
Make page source a little bit more readable.
|
|
The main aim is a more logical DOM structure and more performant CSS.
|
|
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).
|
|
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.
|
|
400x400 is a waste, given that the size of the logo set by CSS is either
100x100 (wide) or 200x200 (narrow).
|
|
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.
|
|
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.
|
|
|
|
Tested on iPhone 6 Plus (both portrait and landscape).
|
|
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.
|
|
|
|
The way I handle line numbers and the pre block in general is inspired
by the MDN wiki. See, for instance,
https://developer.mozilla.org/en-US/docs/Web/JavaScript/A_re-introduction_to_JavaScript
a screenshot is here: https://i.imgur.com/982TBDc.png
Also tweaked other styles, e.g., changed the primary monospace font to
Consolas, and slightly tweaked a few old posts.
|
|
|
|
(other than index.html).
|
|
|
|
by replacing http://fonts.googleapis.com with ://fonts.googleapis.com .
Credit goes to http://goo.gl/KWcZJu .
|
|
|
|
Among other fixes and tweaks.
|
|
Also tweaked icons a bit.
Note that this commit doesn't really work: I implemented a "stoppable
HTTP Server" here to be stopped when "mother process" receives
SIGINT (i.e., KeyboardInterrupt), without realizing that all porcesses
get SIGINT. Therefore, the custom server is hardly needed.
See http://git.io/vJ9yA for more information.
(This implementation has some value tought, that's why I'm committing to
keep it in history.)
|
|
Also fixed several problems:
1. Rending SVG and making it a clickable link is basically impossible
across multiple browsers. I'm now using a pretty good PNG;
2. Implemented new_post in pyblog;
3. Footnotes related updates to the theme.
|
|
Note that I'm using an <embed> tag with the svg because if wrapped in
<img>, the svg won't render on Safari. After using the <embed> tag, the
svg renders on all four major browsers on OS X (Chrome, Safari, Firefox,
Opera), and it looks nice on all three but Firefox, in which case it's
crappy as fuck.
|
|
Mainly generating feed and index.
|
|
Also wrote pyblog that currently can generate parts most of the blog.
|