rdebeasi

#!/bin/sh

# For even easier syncing, put the file in ~/bin and alias this script to gs:
# alias gs='gsync.sh'

# If any step fails, abort the script.
set -e
echo "Pulling..."
git pull --no-edit
echo "Pushing..."

rdebeasi

/* Simple 4-col tiny grid - designed as a companion to the Bootstrap grid
   Overrides Bootstrap's default stacking behavior for "tiny" devices (<=400px).
   Feel free to change this breakpoint to match your needs - 767px is probably a more natural fit with Bootstrap defaults.
   Made with love in PROD - http://www.prod4ever.com/ */

@import "variables.less";
@import "mixins.less";

/*  Utility Classes
    Tiny grid is a subest of the phone grid, so visible-phone and hidden-phone apply to tiny devices as well. */

rdebeasi

@import "mixins.less";
@import "variables.less";

.grid-no-gutter {
  /* Removes margin from Bootstrap Grid. This class goes at least one level above row-fluid.
  Works in Bootstrap 2. In Bootstrap 3, #grid has been removed. */
  #grid > .fluid( percentage( 1 / @gridColumns ), 0 );
}

rdebeasi

export PATH=/opt/subversion/bin:~/bin:/opt/local/bin:/opt/local/sbin:~/Documents/util/scripts:$PATH
# Pyhton virtualenv
export WORKON_HOME=~/Envs
source /usr/local/bin/virtualenvwrapper.sh
# Use Sublime Text as editor
export EDITOR='subl -w'

# Commands
alias gs='gsync.sh'
alias vhost='subl /etc/hosts /Applications/MAMP/conf/apache/extra/httpd-vhosts.conf'

rdebeasi

@import "mixins.less";
@import "variables.less";

@media (min-width: 400px) and (max-width: 767px) {
  /* Restore standard bootstrap grid for medium-sized devices. */
  #grid > .fluid(@fluidGridColumnWidth768, @fluidGridGutterWidth768);
}

rdebeasi

:nth-child(4n+1) {} /* - For 1, 5, 9, 13...*/
:nth-child(4n-2) {} /* For 2, 6, 10, 14... */
:nth-child(4n-1) {} /* For 3, 7, 11, 15... */
:nth-child(4n) {} /* For 4, 8, 12, 16... */

rdebeasi

#!/bin/sh
 
echo "~*~*~ IT'S GO TIME!!! ~*~*~"
echo "Collecting static files..."
python manage.py collectstatic --noinput
echo "Adding & committing..."
git add staticfiles
git commit -m "Collected static files."
# If the push to origin fails, abort the script. It's ok if the commit fails: the user might not have had any static file changes to commit.
set -e

rdebeasi

// ----
// Sass (v3.3.0.rc.3)
// Compass (v1.0.0.alpha.18)
// ----

%placeholder {
  color: blue;
}

@mixin dostuff($color: red){

rdebeasi

@echo off
:: the "2>NUL" surpresses error messages. Web workbench executes autorun
:: but does not have access to sublime text or meld, so it throws errors.
2>NUL doskey subl="C:\Program Files\Sublime Text 3\sublime_text.exe" $*
2>NUL doskey opendiff="C:\Program Files (x86)\Meld\meld\meld.exe" $*
2>NUL doskey open="explorer" $*
2>NUL doskey ajaxmin="C:\Program Files (x86)\Microsoft\Microsoft Ajax Minifier\ajaxmin.exe" $*

rdebeasi

Original question: But how do you make clients consider your advice? If they don't like what you have to say, that's fine. Do you ever have clients who think they are designers? (On Designer News)

---

At the beginning of a project, I try to get a sense of what the client wants: general goals, websites or apps they like, etc. Then when problems come up, I try to explain them in terms of the client's goals.

For example: "You mentioned that you want the focal point of the page to be the 'buy' button. The copy that you gave me is a little long and would push the buy button offscreen for most users. What do you think about shortening the copy so that it's easier to see the buy button?"

Or: "The navigation that you proposed totally makes sense in light of your product lineup, but I'm worried that it might be confusing to users who aren't already familiar with your products. That shopping site