brigleb

Of course you need grunt to start with. And then...

Solid

• grunt-contrib-watch
• grunt-contrib-uglify
• grunt-contrib-imagemin
• grunt-contrib-sass (or use faster/better grunt-sass?)
• grunt-contrib/jshint
• grunt-autoprefixer

brigleb

module.exports = function(grunt) {

  // Project configuration.
  grunt.initConfig({
    pkgc: grunt.file.readJSON('package.json'),

    // Watch files that may change and should trigger updates
    watch: {
      sass: {
        files: ['sass/*.{scss,sass}', 'sass/**/*.scss'],

brigleb

I have some reading for you guys.

1. Be sure you get SSH and the keys. http://opensourcehacker.com/2012/10/24/ssh-key-and-passwordless-login-basics-for-developers/
2. We will at points in our lives be using pull requests more/again. Read chapter 10 of Git in Practice, that book we just got and is sitting out here. It covers PR's and how to use them from the command line.
3. Read up on tmux sometime, I think it would save us all a lot of time. http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/tmux.1
4. In time, I am hoping we can move more toward Bourbon, Neat, and Bitters. http://bourbon.io/ Please look into those. Thoughtbot are really bright people. Trust me on that one.
5. Remember that we also have an excellent Grunt book. I'd like us to improve our use of Grunt in our workflow, and add our best version to our fork of Underscores. (see http://mattbanks.me/grunt-wordpress-development-deployments/ for ideas)

Helpful developer resources

brigleb

{
  "sample": {
    "themes": [
      "woothemes/storefront"
    ],
    "mu_plugins": [
      "woocommerce"
    ],
    "plugins": [
      "wp-retina-2x",

brigleb

Set up VVV

Start with these instructions and you should have a site running. You want to use the WordPress Stable setup...

All WordPress admin usernames and passwords for WordPress installations included by default are admin and password.

• WordPress user: admin
• WordPress pass: password
• LOCAL PATH: vagrant-local/www/wordpress-default
• VM PATH: /srv/www/wordpress-default
• URL: http://local.wordpress.dev

brigleb

Our goal is to have a special branch (one or more) matching a production environment. Using a service like Beanstalk, you want to be able to push to one of those branches, and have it end up at the server with compiled Sass, JavaScript, image, and other assets. You're unable to run your tools on the server, but you want to keep your repository free from these messy compiled assets.

Let's assume we're using a kind of Gitflow methodology, and that our branch for deployment will be called staging.

You have been doing your work on the develop branch... or wherever...

1. Check out your branch.

git checkout staging

brigleb

For WordPress

• Underscores theme
• JetPack plugin

For Front-end Theming

• Sass
• Compass
• Team Sass Toolkit

brigleb

One of the most important concepts to understand at Needmore is Kaizen. This means continual improvement. Apply this to everything you see below. The following are just guidelines, part of your job is to keep improving, getting better, refining the process, learning, and teaching.

Your goal as a member of the Needmore team is to feel empowered to make sure that you continue to improve, and we do as well. We don't expect you to do something just because it's written here, we expect you to do it better. Learn how to improve the process to end up with a better result, with less mistakes, with less problems. Don't keep doing something a certain way because that's the way we've been doing it.

There are six key aspects to being a successful, productive part of development at Needmore.

Process

Get comfortable using Trello for development and issue tracking. Make sure you use it in a way you can keep the whole team in the loop at all times. Remember to notify the project manager when making changes tha

brigleb

body.single-peopleandplaces {
  .wrap .photo {
    height: ( $photoheight / 2 );
    width: 100%;
    @include bp(medium) {
      height: ( $photoheight * .75 );
      width: ( 100% / 2 );
    }
    @include bp(large) {
      height: $photoheight;

brigleb

The goal here is to have a script of some kind that lets you "deploy" your WordPress theme to GitHub, and the auto-updater plugin that supports GitHub will then pull the latest tagged release on your master branch onto your website.

We want to try replacing FTP-based methods for deployment, while having a record of each deployment to our sites. Presumably, this would be more useful for the "staging" site. On the production site, you might want to update the theme in a more manual (and less frequent) fashion.

1. Update version number in style.css and elsewhere.

I am theorizing that we want to increment a global variable in functions.php

2. Checkout master branch, merge