mikeumus

Take these courses to get web dev savy, in order:

• http://discover-devtools.codeschool.com/ - Become a DevTools Ninja.
• http://try.github.io/ - Git skillz...
• http://try.jquery.com/ - quality jQuery knowledge.
• https://www.khanacademy.org/computing/cs - Easiest to follow, free, most in-depth going into advanced Javascript.
• https://university.mongodb.com/ - mongoDB is the hotness for modern, sexy web apps.

All of these courses result in badges or symbols of course completion. Specifically the CodeSchool courses have OpenBadges awarded for example here's my CodeSchool "Report Card" page: https://www.codeschool.com/users/705399

derek

Scenario

I want to use YUI inside of a WebWorker thread. Flickr recently wrote a post on this very topic, Web workers and YUI.

Problem

But I want to use YUI's CDN, which WebWorkers prevent because it enforces a same-origin policy with importScripts()

Solution

balupton

	# =================================
	# DocPad Events

	# Here we can define handlers for events that DocPad fires
	# You can find a full listing of events on the DocPad Wiki
	events:

		# Server Extend
		# Used to add our own custom routes to the server before the docpad routes are added
		serverExtend: (opts) ->

visualjeff

# Docker version 1.1.2, build d84a070
FROM    ubuntu:14.04

RUN apt-get update && apt-get install -y \
    git \
    software-properties-common \
    python-software-properties \
    make\
    gcc \
    g++ \

balupton

DocPad: Bundle your scripts with Browserify

The following will bundle your script assets with browserify each time a generation write completes. The bundled file will be located at my-website/out/scripts.js if you are using all the default configuration for your paths.

Installation

1. Install Dependencies

ntotten

:: 3. Build DocPad Site
echo Building the DocPad site
pushd %DEPLOYMENT_TARGET%
call  %DEPLOYMENT_TARGET%\node_modules\.bin\docpad.cmd generate
IF !ERRORLEVEL! NEQ 0 goto error

ntotten

#!/bin/bash

# ----------------------
# KUDU Deployment Script
# ----------------------

# Helpers
# -------

exitWithMessageOnError () {

balupton

Moving DocPad Forward, the rise of backend-agnostic GUIs

A GUI, or rather a CMS interface for DocPad is the big next step. It was also one of the first proof of concepts I used to ensure DocPad would be able to scale into the web development platform of the future.

Proof of Concept

Back in the first early months of DocPad, I created three plugins:

• Authenticate: To authenticate you against the project's maintainers to ensure that you have read and write access
• REST: Provided authenticated users the ability to update documents via HTTP POST requests using JSON

mikeumus

#!/bin/bash
# Run this script like this: 
# curl http://bit.ly/git-me | sh

cat > ~/.gitconfig <<EOF
[user]
  name = mikeumus
  email = mikeumus@gmail.com
[alias]
  co = checkout

johan

/* Examples:

Use grep with two arguments to find inherited or direct properties of an object:

> grep(document, 'get') // see all properties case insensitively matching *get*:
{ getCSSCanvasContext: function getCSSCanvasContext() { [native code] }
, getElementById: function getElementById() { [native code] }
, getElementsByClassName: function getElementsByClassName() { [native code] }
, getElementsByName: function getElementsByName() { [native code] }
, getElementsByTagName: function getElementsByTagName() { [native code] }