Choosing to use one tool over another is one of the largest challenges developers face. Regardless of what you’re choosing, be it a code editor, a framework, or even a build tool. It’s never an easy decision.
When it comes to build tools, the two most popular options right now are Grunt and Gulp. But are these the only two you should choose from? If not, what other choices do you have?
Let’s answer this question.
Most tools that help you automate your workflow require the use of the command line. Hence, the first obstacle you have to overcome is getting comfortable with the command line.
But the command line is scary.
Playing with it feels like you’re dismantling a bomb that could go off any moment. One wrong move and that’ll mean the end of your life, and your computer.
I didn’t dare to touch it when I first began to code. I felt that the command line was a tool that only experts could use.
However, as I got to know more about it, I began to realize that the command line isn’t scary at all! It’s incredibly safe, even for beginners, and anyone can use it to help improve their workflow.
In this article I’ll show you why the command line isn’t that scary, and how to start to get comfortable with it.
Ready to go? Let’s begin!
Bower is a great dependency manager that’s specially created to help you manage different frontend libraries.
It reduces the time and energy you need to spend hunting around the web for libraries like Susy and jQuery by helping you install, update or delete them with a single command.
To top it off, it can help you download all the libraries you need whenever you scaffold a new project with a single command.
In this article we’ll talk about how to install Bower and how to use it.
A good workflow is crucial for development because it saves time. We know this, and yet we constantly procrastinate this important task.
We can’t blame ourselves really. New technologies pop up and we have no idea how to use them. The web industry moves too fast and sometimes causes us to be completely overwhelmed.
So for the first post in the workflow series, I wanna show you what a development workflow is, and how to automate different parts of the workflow.
Two weeks ago, I said I wanted to write about a new topic in addition to Susy. I had 3 major themes in mind and wanted to find out if you’d be interested in them. So I posted up a survey and asked for feedback.
After two weeks of non-stop email interviews, as well as from the survey results, I’m happy to announce that I’ve came to a conclusion on what to write about next.
I think you’ll be excited to hear this!
Susy has a
gallery() mixin that helps us create galleries easily. It abstracts away a lot of complexity.
Because of this abstraction, it sometimes leaves people puzzled about why something isn’t working. This often boils down to two problems.
This post reveals the two problems and shows you how to solve them.
I have only written about Susy since the release of Learning Susy a few months ago. I’ve been working on the update since then and now that it’s finally complete, I wanna move on to a new topic.
There are 3 themes that I’m interested to explore and I’ll need your help in choosing which one to work on.
But first, let me be completely honest to you about my feelings for the past few months.
This article is here to help you out if you’re having trouble using Masonry with Susy.
I have been using Breakpoint to handle my media queries for a long time and I have been happy with it. However, during my previous project, I discovered that I needed something more.
Since I was working on rebuilding my starter template for Learning Susy, I went about hacking my own breakpoint mixin that satisfied all my needs. I thought you’d be interested to hear what I came up with :)
I wrote about configuring Grunt to use LibSass with Susy in the last article and feedback has been amazing. There were multiple requests for me to write another article to use LibSass with Gulp instead, so here it is :)