Jeremy Felt

Posts

For things with titles.

Follow via RSS

Deployment Workflows Wrap-up

This is a wrap-up post for the last few days I spent documenting a series of deployment workflows I use to get code into production. While writing all of this up over the last several days, I was able to compile some of my thoughts about what a proper workflow should look like. I’m not […]

Deployment Workflows, Part 4: WSU Spine

This post is the fourth in a series of deployment workflows I use to get code into production. This is the one non-WordPress deployment writeup, though still interesting. The WSU Spine plays the role of both branding and framework for websites created at WSU. It provides a consistent navigation experience, consistent default styles, and the […]

Deployment Workflows, Part 3: WSU Indie Sites

This post is the third in a series of deployment workflows I use to get code into production. While the WSUWP Platform is the preferred place for new sites at WSU, there are times when a single site WordPress installation is required. Until about February of 2014, all new sites were configured on our WSU […]

Deployment Workflows, Part 2: jeremyfelt.com

This post is the second in a series of deployment workflows I use to get code into production. The site you’re reading this on is often a neglected playground of sorts. I’ll run into an interesting method of provisioning the server or maintaining code, apply it halfway and then get distracted with something else. Hearting […]

Deployment Workflows, Part 1: The WSUWP Platform

This post is the first in a series of deployment workflows I use to get code into production. Many of my weekdays are spent working on and around the WSUWP Platform, an open source project created to provide a large, multi-network, WordPress based publishing platform for universities. Conceptually, a few things are being provided. First, […]

Jeremy's profile photo: a selfie taken while walking through Berlin.

Jeremy Felt wrote this and published it on the internet.

Unless otherwise expressly stated, the content above is licensed under a CC BY-SA 4.0 International License.