markjaquith

<?php

// Change /*CUSTOMIZE_THIS*/ to a unique name (two places). Go ahead, make it long.
// Like, your initials, and your full plugin name.
// e.g. MTJ_Some_Awesome_Plugin_Controller

/*CUSTOMIZE_THIS*/_Controller::init();

class /*CUSTOMIZE_THIS*/_Controller {
	function init() {

ChrisWills

# GNU Screen - main configuration file 
# All other .screenrc files will source this file to inherit settings.
# Author: Christian Wills - cwills.sys@gmail.com

# Allow bold colors - necessary for some reason
attrcolor b ".I"

# Tell screen how to set colors. AB = background, AF=foreground
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'

vasilisvg

#HTML presentation tools

There are many HTML presentation tools and they are all created for slightly different reasons. Here's an overview. Please let me know if I forgot any.

##CSSS

CSS-based SlideShow System

• Source
• Example

jxson

Synopsis

At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)

Code Example

Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.

Motivation

AstonJ

#get root access
$su -
$ cd /tmp

#Remove old Ruby
$ yum remove ruby
 
# Install dependencies
$ yum groupinstall "Development Tools"
$ yum install zlib zlib-devel

johnpbloch

# Will produce command line prompts like
#         directory(branch) $
# in git repositories and like
#         directory $
# elsewhere.
# If there are unstaged changes in the repository, there will be an asterisk next to the branch name:
#         directory(branch*) $

parse_git_branch() {
	hasmod=""

chriscoyier

@media only screen and (min-width: 320px) {

  /* Small screen, non-retina */

}

@media
only screen and (-webkit-min-device-pixel-ratio: 2)      and (min-width: 320px),
only screen and (   min--moz-device-pixel-ratio: 2)      and (min-width: 320px),
only screen and (     -o-min-device-pixel-ratio: 2/1)    and (min-width: 320px),

aaronjorbin

Purpose

The purpose of this document is to start a discussion that leads to better expectations between speakers and organizers of WordCamps. It is based on Open Conference Expectations by @rmurphey @divya and @paul_irish. It is based on my experience speaking at many WordCamps and seeing some great things and not great things. I would love your comments and feedback.

What I ask for as a speaker

1. A complimentary ticket to the event.
2. A code of conduct for every attendee, including speakers and sponsors. Everyone should be able to have a good time in a safe, harassment-free environment. See the The Ada Initiative for more information on how to create such a policy.
3. Adequate amount of time to prepare. This means the call for speakers should occur at least sixty days before the camp and invitations at least thirty days before the

billerickson

<?php

/**
 * Don't Update Plugin
 * 
 * This prevents you being prompted to update if there's a public plugin
 * with the same name.
 *
 * @since 1.0.0
 * @author Mark Jaquith

suhajdab

#include <Adafruit_NeoPixel.h>

#define PIN 2
#define Pixels 24
#define BG 1

// Parameter 1 = number of pixels in strip
// Parameter 2 = Arduino pin number (most are valid)
// Parameter 3 = pixel type flags, add together as needed:
//   NEO_KHZ800  800 KHz bitstream (most NeoPixel products w/WS2812 LEDs)