nilsjesper

curl -s -b -N --location http://www.nytimes.com/2016/11/23/us/politics/trump-new-york-times-interview-transcript.html \
| perl -0ne 'my @list = $_ =~ m/>TRUMP:(.*?)<\/p>/smg; print $list[rand @list]' \
| say  -i -r 300 -v Alex

hakimelek

[
  {
    "institution": "Alabama A & M University"
  },
  {
    "institution": "University of Alabama at Birmingham"
  },
  {
    "institution": "Amridge University"
  },

adamreisnz

{
  "name": "project-name",
  "description": "Template for static sites",
  "version": "1.0.0",
  "homepage": "http://www.project-name.com",
  "author": {
    "name": "Adam Reis",
    "url": "http://adam.reis.nz"
  },
  "license": "UNLICENSED",

tony-jones

{
  "name": "jekyll-starter-kit",
  "version": "1.0.0",
  "description": "jekyll, asset build using npm scripts",
  "main": "src/scripts/main.js",
  "scripts": {
    "eslint:dist": "eslint src/scripts/*.js",
    "eslint": "npm run eslint:dist",
    "uglify:dist": "uglify -s src/scripts/*.js -o dist/scripts/main.min.js",
    "uglify:_site": "uglify -s src/scripts/*.js -o _site/dist/scripts/main.min.js",

bastianallgeier

Kirby + Patterns = <3

When I heard about Brad Frost's Patternlab for the first time at beyond tellerrand I was intrigued. The idea of splitting your design work for a website into simple modules or patterns isn't new and starts to become more and more of a standard. But organizing this into a very visual styleguide/patternlab seemed to make so much sense. Brad also introduced a very interesting approach with his separation of modules into categories, such as atoms, molecules and organisms.

I started porting Brad's patternlab app to Kirby, but it never really made it to something polished and it turned out for me after using it for Kirby's panel UI, that it's actually a pain in the ass to maintain such a pattern collection.

The problem of patternlab

The problem with such a styleguide or patternlab is that it exists next to the real thing. When you change something in your code base you also have to update the particular code for the pattern in patternlab. To be honest I went very quickly from being

plasticbrain

/*******************************************************************************
 * Description:
 * 
 *   Gulp file to push changes to remote servers (eg: staging/production)
 *
 * Usage:
 * 
 *   gulp deploy --target
 *
 * Examples:

mpneuried

_data = 
  foo: 23
  bar: 42
  bazz: null

$.ajax
	url: _path
	type: "POST"
	data: JSON.stringify( _data )
	contentType: "application/json; charset=utf-8"

PurpleBooth

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

tmaybe

How to Ignore Merge Conflicts for Specific Files in a Git Repository

Create a directory and git init it

$ mkdir merge-test
$ cd merge-test/
$ git init

chantastic

Hi Nicholas,

I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:

The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't