{"id":279119,"date":"2018-12-14T08:59:17","date_gmt":"2018-12-14T15:59:17","guid":{"rendered":"http:\/\/css-tricks.com\/?p=279119"},"modified":"2018-12-15T07:00:34","modified_gmt":"2018-12-15T14:00:34","slug":"annotated-build-processes","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/annotated-build-processes\/","title":{"rendered":"Annotated Build Processes"},"content":{"rendered":"

When you’re putting together a build process for a site, it’s so dang useful to look at other people’s processes. I ran across Andrew Welch’s “An Annotated webpack 4 Config for Frontend Web Development”<\/a> the other day and was glad he blogged it. If I was kicking off a new site where I wanted a webpack build, then I’d almost certainly reference something like this rather than start from scratch. At the same time, it made me realize how build processes all have such different<\/em> needs and how unique those needs are now from even a few years ago in the hay day of Grunt and Gulp build processes.<\/p>\n

<\/p>\n

I was looking around for an annotated Gulp reference file and came across another one of Andrew’s articles — “A Gulp Workflow for Frontend Development Automation”<\/a> — from just one year earlier! Here’s a simplified list of what he was doing with Gulp (which he explains in more detail in the post):<\/p>\n