Whether you work alone or on a large team, following a solid development workflow will help you get it up in production without bringing production down.
I have seen my share of Server 500 errors while making a “quick” code change in production. Then I committed to finding and following best practices in development in order to avoid the “sweat-inducing, hold your breath, 2 minutes is eternity” feelings that a missing semi-colon can produce. What I found was a workflow that moved code from a local environment, to a staging environment, and then to production without creating a lot of extra work.
In this session, we’ll discuss how we developed this workflow and the tools we use to streamline the process. While the focus of many of the tools we will share are for WordPress, the process and ideas are relevant for all developers.
Aaron ForsythAcademic Technologies Developer
Aaron Forsyth has been employed in various distributed IT units at UNC Charlotte for the last 10 years. In 2010 he began dabbling in web development and dove into WordPress shortly thereafter. Forsyth is currently working as the Academic Technologies Developer for the College of Liberal Arts & Sciences where he focuses on WordPress development. He holds a BA in Mathematics and an MS in Information Technology from UNC Charlotte.
Alexander ChapinExecutive Director of Academic Technologies, UNC Charlotte College of Liberal Arts & Sciences
Alex Chapin is the executive director of Academic Technologies for the College of Liberal Arts & Sciences at UNC Charlotte. He has been involved with the design and development of technologies for teaching, learning and research for over 15 years at a number of institutions including Columbia University, University of Virginia, Middlebury College and UNC Charlotte.