Automating your workflow zell free ebook download

Examples and Use Cases Technology Considerations. Get White Paper. Download one of our ebooks or white papers to learn more about Integrify. Wacker Dr. Failed to load latest commit information.

View code. Usage Scaffolding Add files manually What is this repository for? Usage Run bower install. Run npm install. Run gulp for development.

It took me months of trial and error to get the workflow I created for myself today. Note: Hey! AYW was written 2 years ago.

Here, we walk through the basics of automation and show you things you need to know before you begin the journey. This will be where you get knowledge of things like the command line, what goes in a development workflow, and how to use Gulp.

We begin building the automated workflow at this phase, starting with the process of removing tedious and manual tasks you do. You will also learn how to use tools many modern tools for development. You will learn what to test for, and how to test your code with you having to eyeball them manually. You'll learn how to get a machine to test your code whenver you push it to a remote repository. Here, you'll ensure that you don't have to worry about your website breaking without knowing it.

This is where you prepare your website for production. We reduce your asset sizes and do everything we can to make sure your website is wicked fast. What's more, everything will be done in one simple step so you don't forget anything.

The deployment phase shows you different ways to deploy your website quickly onto your servers without having copy and paste your files by FTPing in manually. Updating your site becomes less of a headache. Here, you'll learn how to use the workflow with other projects. You'll also learn how to update project dependencies easily. In the last section of the book, we go through how to organize your Gulpfile, how to find good plugins to use and what to do next after you've completed the book.

Bonus 1: Creating your own Gulp plugin You never have to wait for someone else to create a plugin you desperately need once you learn how to do so. For example, I created my own plugins to create PDF, ePub and Mobi versions of this book because nothing else out there seemed to work.

One more thing. You probably have different environments like development, staging and production set up. Developing and seeing your changes straight in the browser is definitely one of the most awesome automations you can do in the development stage. Doing so requires you to learn how to use a build tool, like Grunt or Gulp. The first kind of test is code format tests, where you check your code formatting to see if they follow industry practices using tools like JShint and SCSSlint. The third type of tests is CSS Regression testing, where you check the output of the browser to see whether it breaks parts of the page that you have previously coded.

These tests helps catch visual errors on even on parts of the site that you may fail to notice yourself. They require you to learn more stuff, like PhantomCSS and more. Integration is normally done purely with Git, where you push, pull and merge code from different developers into a single repository. To do so, you can set up a continuous integration CI , which basically means automated testing after you integrate the codebase.

You can also optionally amend your file structure such that production assets are placed in a specific folder. This is the process where you push your code and assets into the server and allow the changes you make to be viewed by the public.

A more modern method is to ssh into the server and do a git pull, which removes a ton of hassle already. An automated way would be to create a post-receive hook where your server automatically pulls the new project whenever there is an update.

I hope this article has given you more clarity on what to expect and what to learn in this jargon-filled dev world. What would you like to automate for your own workflow?