Using Roots 7.0 with Git deploy

sage
5

I have been relentlessly practicing this new Git deploy workflow to demonstrate it at my upcoming talk at WordCamp LAX. This is what I have and please let me know if I am making any errors or being redundant. I am primarily a designer and front-end developer, so I am learning as I go along with a lot of these new technologies Roots has been adopting.

###Services/Software used

For the purposes of this example, I am renaming the theme as ‘demo’.

####Part I: Github setup

  1. Create a repository at github.com named ‘demo’
  • Clone Roots repository from github.com to desktop as ‘demo’
  • Change local Roots clone settings as follows:
    • Change Primary remote repository (origin) to: https://github.com/shaimoom/demo.git (from github.com repo)
    • Delete the following from Ignored files (.gitignore):
      • assets/css/*main*.css
      • assets/js/*scripts*.js
      • assets/js/vendor/modernizr.min.js
      • assets/manifest.json
  • Sync the local and remote repositories (initial commit)

####Part II: Local Dev Setup, Install Dependencies & Grunt

  1. Add define('WP_ENV', 'development'); to the WordPress installation wp-config.php
  • Right-click on the ‘demo’ repository in Github and select ‘Open in Terminal’
  • Run npm install on theme root directory (vendor assets will be added to the theme)
  • Run grunt watch on theme root directory in terminal to track changes
  • Activate theme
  • Customize theme

####Part III: Deployment

  1. Remove define('WP_ENV', 'development'); in the WordPress installation wp-config.php
  • Run grunt build and commit in Github (minified assets will be generated for production)
  • Add SSH & SFTP info to Deploy (including theme file path)
  • Deploy from latest commit
  • Activate theme on production site
  • Win?

Repeat Part II and Part III during local development.

Your comments are appreciated.