The usual suspects

• Install homebrew
• Install brew-cask
• Install yeoman

Note: keep an eye on Bedrock as a stack setup.

Build local environment

brew cask install virtualbox

brew cask install vagrant

git some [email protected]:Automattic/vip-quickstart.git

./bin/vip-init

Requires access to WordPress SVN to sync developer plugins

• Updating Shared VIP plugins Checks for WordPress.com username at https://vip-svn.wordpress.com:443

Let's try VVV by 10up instead:

vagrant plugin install vagrant-hostsupdater

git some git://github.com/10up/varying-vagrant-vagrants.git vagrant-local

cd vagrant-local

vagrant up

Note: look into how to have more than one VM set up this way. Possibly vvv-init?

Install starter theme/framework

cd www/wordpress-default/wp-content/themes

Use _s to start until custom baseline can be developed.

Try using Yeoman _s generator

npm install -g generator-wp-underscores

mkdir theme-name && cd $_
yo wp-underscores

grunt

Note: Roots and Bones are worth a look too.

Hacked a few bits out of the Roots starter theme with success. Modularity of template files, some sensible functions, and a clean directory structure. Just wish it didn't come with Bootstrap baked-in.

Develop custom theme/site

Following FED standards, of course. Either develop theme in /wp-content/themes directly, or in a separate location/repository and include in /wp-content/themes as a submodule.

grunt
bower

Hardcore mode: Genesis Framework + Dynamik Website Builder + Toolset

Deploy to Staging environment and test/demo

git-ftp? capistrano? grunt? 

Tried grunt-ftp-deploy which worked well enough (as long as you were careful with the ignore settings) although not really suited for use whilst developing, as it doesn't track file changes and uploads the entire project each time. grunt-git-ftp could be an option, or possibly Dandelion, both of which use git to track changes.

Package finished theme for deployment

grunt

Deploy to Production environment

git-ftp? capistrano? grunt?