Zach Harkey zachharkey

## Ruby.sublime-build
# Get Sublime Text to use your rvm ruby without hardcoding a `$USER`.
#
# Include the configurations below the commend in the appropriate file listed below:
#
#  - OS X ST2: ~/Library/Application Support/Sublime Text 2/Packages/Ruby/Ruby.sublime-build
#  - OS X ST3: ~/Library/Application Support/Sublime Text 3/Packages/User/Ruby.sublime-build
#  - Linux ST2: ~/.config/sublime-text-2/Packages/Ruby/Ruby.sublime-build
#  - Linux ST3: ~/.config/sublime-text-3/Packages/User/Ruby.sublime-build

{

## README.md

      
              2 files
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                zachharkey
                / README.md
            
            
              Created
              May 23, 2013 06:19
                — forked from necolas/README.md
            
          
    Template Components

Used to provide structural templates.
Pattern
t-template-name
t-template-name--modifier-name
t-template-name__subcomponent-name--subcomponent-modifier-name


## Sample-Post.html
<p>This is a sample post. It is designed to test the presentation of range of standard content elements. To be specific, these are the non-structured, elements that would make up the main content of a generic page, post, or article. This content is CMS agnostic and Markdown-friendly. A properly configured editor should support (and perhaps even be limited to) the set of elements on this page.</p>
<h2 id="this-is-a-major-heading-h2">This is a major heading (h2)</h2>
<p>If you peek at it with a web inspector, you'll see that it is an <code>H2</code>. There should only be one first level heading per page and it should be reserved for the page title itself. In most CMSes this title field is separate from the main content body and its placement is controlled at the template level, ideally with a custom class attribute. Consult the <a href="http://html5doctor.com/outlines/">HTML5 outlining algorithm</a> for best practice.</p>
<p>There's nothing stopping you from using <code>H3</code>, <code>H4</code>, or <code>H5</

## _media-object.scss
// OOCSS Media Object
@mixin media-object($img: '.media-img', $bd: '.media-bd', $margin:10px, $position: left, $formatting-context: 'overflow') {
  @include pie-clearfix; // or extend a .clearfix class
  #{unquote($bd)} {
    @if $formatting-context == 'overflow' {
      overflow:hidden;
    } @else {
      display:table-cell;
      width:10000px;
      *width:auto;

## gist:4152430

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                zachharkey
                / gist:4152430
            
            
              Created
              November 27, 2012 04:44
                — forked from lucasfais/gist:1207002
            
              
                Sublime Text 2 - Useful Shortcuts
              
          
    Sublime Text 2 – Useful Shortcuts (Mac OS X)

General


		 ⌘T 
		 go to file 
	
	
		 ⌘⌃P 
		 go to project 
	
	
		 ⌘R 
		 go to methods 
	
	
		 ⌃G 
		 go to line 
	
	
		 ⌘KB 
		 toggle side bar 
	
	
		 ⌘⇧P 
		 command prompt 
	

## _shared.scss
// Using this structure, this file should be your canonical stylesheet where
// everything would be imported into, so that you can just `@import "shared";`
// in both your normal and IE stylesheets, only having to add libraries and
// such in one place.

// These styles are just a contrived example.
body {
  font-size: 18px;
  @include respond-to(desktops) {
    color: blue;

## html.tpl.php
<!DOCTYPE html>
<html<?php print $html_attributes; ?>>
<head>
  <?php print $head; ?>
  <title><?php print $head_title; ?></title>
  <?php print $styles; ?>
  <?php print $scripts; ?>
</head>

<body<?php print $body_attributes;?>>
	# Get Sublime Text to use your rvm ruby without hardcoding a `$USER`.
	#
	# Include the configurations below the commend in the appropriate file listed below:
	#
	# - OS X ST2: ~/Library/Application Support/Sublime Text 2/Packages/Ruby/Ruby.sublime-build
	# - OS X ST3: ~/Library/Application Support/Sublime Text 3/Packages/User/Ruby.sublime-build
	# - Linux ST2: ~/.config/sublime-text-2/Packages/Ruby/Ruby.sublime-build
	# - Linux ST3: ~/.config/sublime-text-3/Packages/User/Ruby.sublime-build

	{
	<p>This is a sample post. It is designed to test the presentation of range of standard content elements. To be specific, these are the non-structured, elements that would make up the main content of a generic page, post, or article. This content is CMS agnostic and Markdown-friendly. A properly configured editor should support (and perhaps even be limited to) the set of elements on this page.</p>
	<h2 id="this-is-a-major-heading-h2">This is a major heading (h2)</h2>
	<p>If you peek at it with a web inspector, you'll see that it is an <code>H2</code>. There should only be one first level heading per page and it should be reserved for the page title itself. In most CMSes this title field is separate from the main content body and its placement is controlled at the template level, ideally with a custom class attribute. Consult the <a href="http://html5doctor.com/outlines/">HTML5 outlining algorithm</a> for best practice.</p>
	<p>There's nothing stopping you from using <code>H3</code>, <code>H4</code>, or <code>H5</
	// OOCSS Media Object
	@mixin media-object($img: '.media-img', $bd: '.media-bd', $margin:10px, $position: left, $formatting-context: 'overflow') {
	@include pie-clearfix; // or extend a .clearfix class
	#{unquote($bd)} {
	@if $formatting-context == 'overflow' {
	overflow:hidden;
	} @else {
	display:table-cell;
	width:10000px;
	*width:auto;
⌘T	go to file
⌘⌃P	go to project
⌘R	go to methods
⌃G	go to line
⌘KB	toggle side bar
⌘⇧P	command prompt
	// Using this structure, this file should be your canonical stylesheet where
	// everything would be imported into, so that you can just `@import "shared";`
	// in both your normal and IE stylesheets, only having to add libraries and
	// such in one place.

	// These styles are just a contrived example.
	body {
	font-size: 18px;
	@include respond-to(desktops) {
	color: blue;
	<!DOCTYPE html>
	<html<?php print $html_attributes; ?>>
	<head>
	<?php print $head; ?>
	<title><?php print $head_title; ?></title>
	<?php print $styles; ?>
	<?php print $scripts; ?>
	</head>

	<body<?php print $body_attributes;?>>