Regular (one-line) code inside a `code` tag has some padding around it. This leads to some weird spacing when dealing with code blocks (e.g. inside `pre`).
Removing the horizontal paddings for these. (Also replacing `border: none;` with `border: 0;` because it's shorter)
* jglovier-master: (35 commits)
Fix for menu at mobile again
Fix site footer styles on mobile
Fix for menu not working on mobile
dat breathing room tho (expand site width slightly more)
Replace footer github and twitter link text with inline SVG icons
Post content styles for mobile
Replace unicode menu icon with inline SVG
Adds mobile styling for menu at sub 600px viewport widths
🔥 permalink option so default date permalink method is left in tact
For the love of perf, add syntax.css rules to main.css and call only one stylesheet
Adds another placeholder post to illustrate post content styles
Dem new styles tho
Copy tweaks - brevity FTW
Use class instead of id for CSS specificity ❤️
Add link for RSS subscription
Slightly friendlier and personal date formatting; classes for dem styles, yo
Remove to avoid confusion with site.title
demonstrate use of permalink settings
Add site.url for use in head canonical meta and feed.xml template
Add site.description for use in site head document meta, and feed.xml template
...
- unicode menu icon doesn’t render pixel crisp (has some
anti-aliasing), whereas SVG renders pixel optimized
- using inline SVG (instead of a referenced, attached file, will save
an http request
- Uses new typography, including Helvetica light, larger font-sizes,
and px values
- Wider site width, larger margins, and overall more whitespace
- Responsive down to mobile
Per #964, just upgrade the template site from XHTML to HTML5,
leaving the existing CSS. No need to get fancy.
The HTML is essentially HTML5 Boilerplate. No need for a holy war.
Look and feel should remain the same.
It would really pain me if the default Jekyll site were XHTML. That'd be bad for the internet.
Instead, use Twitter Bootstrap as a base (while still keeping @mojombo's origin design), to give users a great initial baseline to build beautiful, simple sites.
Defaults are more than just the starting point. It's what 80% of users are going to use. Look at WordPress and the default theme. May as well lead by example and start the user off right.
* Add Bootstrap base CSS as a better reset and base layer
* Update default layout to HTML5 with boilerplate best practices
* Add title and post date to post.html (rather than including in the post itself)
* Make site title a variable and add to _config.yml
* Add page title to header
* Add default .gitignore to ignore `_site`
* Remove unused `rss.png` and `.gitkeep`
* Add Modernizr for legacy IE support
kleinfreund
Parker Moore
Jesse shawl
XhmikosR
Joel Glovier
Markus Roth
Josh Brown
Ivan Tse
Edward Ball
Wlodek Bzyl
Benjamin J. Balter