jehoshua02

~/projects/deseretdigital/ksldeals/ksldeals
$ bower install --save deseretdigital-ui/ksl-header#v0.3.3
bower ksl-header#v0.3.3     not-cached git://github.com/deseretdigital-ui/ksl-header.git#v0.3.3
bower ksl-header#v0.3.3        resolve git://github.com/deseretdigital-ui/ksl-header.git#v0.3.3
bower ksl-header#v0.3.3       download https://github.com/deseretdigital-ui/ksl-header/archive/v0.3.3.tar.gz
bower ksl-header#v0.3.3        extract archive.tar.gz
bower ksl-header#v0.3.3       resolved git://github.com/deseretdigital-ui/ksl-header.git#0.3.3
bower ksl-styles#0.0.4          cached [email protected]:deseretdigital-ui/ksl-styles.git#0.0.4
bower ksl-styles#0.0.4        validate 0.0.4 against [email protected]:deseretdigital-ui/ksl-styles.git#0.0.4

jehoshua02

Requests

It all starts with a request. The request is quite simple: some action on some resource with some parameters. I'd like requests to be easy to make and in a format that is easy to construct.

Endpoints

Endpoints represent resources. Example: /dogs, /cats, /users.

I'm curious if a second endpoint to get a single entity (/dogs/:id) is really needed or if we could just piggy back on the collection endpoint (/dogs?ids=[...]). You get guaranteed consistency since there aren't two endpoints to maintain, plus you can get a whole batch using the ids.

jehoshua02

// ----
// Sass (v3.4.9)
// Compass (v1.0.1)
// ----

.media {
  &--ratio-16-9 {
    padding-top: percentage(9/16);
  }
}

jehoshua02

// ----
// Sass (v3.3.14)
// Compass (v1.0.1)
// ----

.media {
  &--ratio-16-9 {
    padding-top: percentage(9/16);
  }
}

jehoshua02

Scripture Schedule

Verses Per Day: 74

Book of Mormon

• Day 1 (2014-01-01): 1 Nephi 1:1 - 3:30
• Day 2 (2014-01-02): 1 Nephi 3:31 - 7:7
• Day 3 (2014-01-03): 1 Nephi 7:8 - 10:15
• Day 4 (2014-01-04): 1 Nephi 10:16 - 13:8

jehoshua02

Many times, when processing a tree, the natural tendency is to reach for a recursive function. But recursive functions can be hard to grok and also run into call-stack issues. Try a queue instead.

For example, I wanted to find all clean tasks in my tasks directory. You just have to tell the queue processing function what to do with each item, and how to collect more items into the queue from each item.

var queue = require('./processQueue');
var tasks = require('require-dir')('.', { recurse: true });
var cleanTasks = [];

var process = function (item) {

jehoshua02

@mixin button-common() {
  border: 0 none;
  color: #fff;
  display: inline-block;
  text-align: center;
  cursor: pointer;
  vertical-align: baseline;
  text-decoration: none;

  &:active,

jehoshua02

var getResponsiveDimensions = function ($element, minWindowWidth, maxWindowWidth) {
  
  minWindowWidth = minWindowWidth || 320;
  maxWindowWidth = maxWindowWidth || 1280;

  var dimensions = {
    minWidth: Infinity,
    maxWidth: 0,
    minHeight: Infinity,
    maxHeight: 0,

jehoshua02

Make a Block Stand Out

Vanilla Markdown

NOTE: This is still a v0 project and anything can change. If there is any wiggle room in the version number saved to your bower.json this could cause breakage when installing in a new environment. Either lock in on a version or embrace spontaneous change.

jehoshua02

The webpack way to load svg?

Every time I use svg images, I want to provide png fallbacks. I was looking into using the file-loader, but I need to do a bit more:

• Move svg and png fallback files into the destination folder.
• Bundle a module for the client to check for svg support.
• Bundle a module for the client that returns the correct url for the image based on svg support.

I hoped there would be an svg-loader but didn't find one in the list. Maybe it's a good idea?