Skip to content

Instantly share code, notes, and snippets.

View captainill's full-sized avatar

Jonathan Thomas captainill

View GitHub Profile
.container {
width: 100%;
margin: 0 auto;
position: relative;
@include from($desktop) {
max-width: $desktop - (2 * $gap);
width: $desktop - (2 * $gap) ;
&.is-fluid {
margin-left: $gap;
/* ==========================================================================
Spacing-specific utilities
========================================================================== */
/**
* Used to adjust the default spacing between components
* Use with great care!
*
* u-<type><direction><size>
*
//psudeo code
var items = {
'ruby': {
name: 'Ruby',
url: '/assets/images...',
workfloadType: 'container',
sentenceAlias: 'Containerized Ruby'
},
'aws': {
@captainill
captainill / main.js
Created January 31, 2017 08:54
example
var items = {
'ruby': {
name: 'Ruby',
url: '/assets/images...'
},
'aws': {
name: 'AWS',
url: '/assets/images...'
}
}
/**
*
*
*/
import BaseStore from 'fluxible/addons/BaseStore';
class RecipeStore extends BaseStore{
static handlers = {
/**
*
*
*/
import BaseStore from 'fluxible/addons/BaseStore';
class ApplicationStore extends BaseStore{
static handlers = {
var path = require('path');
var gulp = require('gulp');
var argv = require('yargs').argv;
var sass = require('gulp-sass');
var gutil = require('gulp-util');
var bless = require('gulp-bless');
var insert = require('gulp-insert');
var concat = require('gulp-concat');
/* global window */
var React = require('react/addons');
var ReactRouter = require('react-router');
var Routes = require('./Routes.react');
var MeStore = require('../../stores/Me');
var MeActions = require('../../actions/Me');
var RedirectActions = require('../../actions/Redirect');
var HistoryLocation = ReactRouter.HistoryLocation;
@captainill
captainill / notes on React Context
Created December 6, 2014 02:21
notes on React Context
Contexts
Summary:
adds `this.context` which you can think of as implicit props, which are passed automatically down the //ownership// hierarchy.
Contexts should be used sparingly, since they essentially allow components to communicate with descendants (in the ownership sense, not parenthood sense), which is not usually a good idea. You probably would only use contexts in places where you'd normally use a global, but contexts allow you to override them for certain view subtrees which you can't do with globals.
The context starts out `null`:
var RootComponent = React.createClass({
render: function() {