All the codes for the future neilrenicker.com. Built with love, late nights, and darker than normal coffee.
- All images are retina-fied using picturefill.js.
- Syntax: date-title-size (example:
130612-on-the-go-small.jpg
,130612-on-the-go-small@2x.jpg
) - Save as progressive
- Run through image minifier
Here are the size templates for common image areas:
- Home page (
img/home
)
- small: 640px w (+ @2x)
- medium: 275px w/h (+ @2x)
- Post pages (
img/posts
)
- large: 900px w
Here are all of the front matter parameters each post needs:
---
layout: article
title: An Older Post
photo: small-strokes.jpg
intro: As I’m working through my apprenticeship at Sparkbox, there are a few ideas that have kept me going when I hit the paralyzing fear of a challenging programming problem.
categories: articles
tags:
- programming
- learning
dsq_thread_id: '1169640142'
css: 2013-07-19-changes
art:
<img class="2013-07-19-sb-neon-on" src="../img/articles/2013-07-19-sb-neon-on.png" alt="Sparkbox Neon Glow">
<img class="2013-07-19-sb-neon-off" src="../img/articles/2013-07-19-sb-neon-off.png" alt="Sparkbox Neon in the Dark">
published: true
---
- If a post is to have custom art direction, the markup should live in front matter called
art:
. Indent markup 2 spaces. It will be included in an otherwise empty, unstyled<div>
with a class ofart-top
. - Custom styles for that post should be placed in a
.scss
file withintemplates/_scss/posts/post-date-and-name.scss
. Sass file should be named the exact name of the post. Update theCSS:
front-matter to match the file name (no extension) of the Sass file. - CSS classes and IDs should begin with
art-
as a module name. Since art directed CSS files are page-specific, there's no need to worry about overlapping styles in the future!