adamstac

// WebKit font-smoothing
//------------------------------------------------

// References:
//
// 1. http://maxvoltar.com/sandbox/fontsmoothing/
// 2. http://maxvoltar.com/archive/-webkit-font-smoothing
//
// Values: none, antialiased (default), subpixel-antialiased
//

kapkaev

require 'faraday'
require 'net/http/digest_auth'


module Faraday
  # Public: A Faraday middleware to use digest authentication. Since order of
  # middlewares do care, it should be the first one of the Request middlewares
  # in order to work properly (due to how digest authentication works).
  #
  # If some requests using the connection don't need to use digest auth you

tsvensen

/* http://www.zeldman.com/2012/03/01/replacing-the-9999px-hack-new-image-replacement/ */
overflow: hidden;
text-indent: 100%;
white-space: nowrap;

eternalstorms

UI- and App Frameworks Evangelist - Jake Behrens, [email protected], twitter: @Behrens
	- What's new in Cocoa
	- Accessibility in iOS
	- Building User Interfaces for iOS 7
	- Getting Started with UIKit Dynamics
	- What's new in Cocoa Touch
	- What's New With Multitasking
	- Best Practices for Cocoa Animation
	- Improving Power Efficiency with App Nap
	- Introducing Text Kit

marioflores

If the deletion has not been committed, the command below will restore the deleted file in the working tree.
$ git checkout -- <file>

You can get a list of all the deleted files in the working tree using the command below.
$ git ls-files --deleted


If the deletion has been committed, find the commit where it happened, then recover the file from this commit.
$ git rev-list -n 1 HEAD -- <file>
$ git checkout <commit>^ -- <file>

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

PaulKinlan

(function() { 
  var CSSCriticalPath = function(w, d, opts) {
    var opt = opts || {};
    var css = {};
    var pushCSS = function(r) {
      if(!!css[r.selectorText] === false) css[r.selectorText] = {};
      var styles = r.style.cssText.split(/;(?![A-Za-z0-9])/);
      for(var i = 0; i < styles.length; i++) {
        if(!!styles[i] === false) continue;
        var pair = styles[i].split(": ");

emiller42

#!/bin/sh

#
# chkconfig: 35 99 99
# description: Node.js /home/ghost/ghost/index.js
#

. /etc/rc.d/init.d/functions

USER="ghost"

chriskjaer

var gulp        = require('gulp'),
    gutil       = require('gulp-util'),
    sass        = require('gulp-sass'),
    csso        = require('gulp-csso'),
    uglify      = require('gulp-uglify'),
    jade        = require('gulp-jade'),
    concat      = require('gulp-concat'),
    livereload  = require('gulp-livereload'), // Livereload plugin needed: https://chrome.google.com/webstore/detail/livereload/jnihajbhpnppcggbcgedagnkighmdlei
    tinylr      = require('tiny-lr'),
    express     = require('express'),

jaicab

.video-container {
  position: relative;
  padding-bottom: 56.25%; /*16:9*/
  padding-top: 30px; 
  height: 0; 
  overflow: hidden;
}
 
.video-container iframe,
.video-container object,