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 :)
Every developer I know has been eagerly awaiting to use LibSass in their development process. When Eric announced that Susy is now compatible with LibSass, I jumped out of my seat and began tinkering with Grunt to create a build process.
Unfortunately, it didn’t work out then :(
The good news is that we can now use Grunt to compile LibSass with Susy without a hitch! I’ll show you how I configured Grunt to use LibSass with Susy in this article.
I mentioned that Learning Susy will be updated with more content by 31st January. Unfortunately, I’m afraid I have to disappoint. I’m sorry.
Letting you down sucks, but it just doesn’t feel right to apologize and shrug it off. I want to be honest about my failures and learnings to make sure that I won’t fail to deliver again. Hence, the reason for this blog post.
Building responsive websites is a must-have skill for front-end developers today. When we speak about responsive websites, the term mobile-first pops into mind immediately.
We know the importance of designing from a mobile-first perspective. Unfortunately, much less was said about coding from a mobile-first approach.
Today, I’d like to share with you about the mobile-first approach to styling, why it is much better, and how to work its magic.
Note: This article will be immensely helpful if you are learning to build responsive layouts with Susy.
It’s been 3 months since Learning Susy has been released and the support from the community has been wonderful. It’s heartening to see so many people start to learn about Susy, and how they have benefited as a result.
I have learned a lot more about what people are looking for since releasing the book through observations, questions and surveys, and I feel that I am now able to make Learning Susy 10x better.
In this post, I’d like to share with you my observations of issues that people often encounter, how I intend to help solve these issues in the next version of Learning Susy, and what all this means to you.
In the last month, I had the privilege of helping a few people find out what went wrong with their Susy code while suggesting a few areas of improvement.
I noticed one problem kept popping up in the questions I answered. People find it difficult to get Susy to work correctly in nested grids. They sometimes employ workarounds that tweak Susy so badly that it hinders instead of helps.
Even though Susy is built to be extremely flexible and easy to use, it has its own key concepts and rules like all other frameworks. You will need to understand these concepts to get Susy to work for you properly.
I’ll like to share one of these concepts with you today to help you overcome a large majority of your Susy problems.
September 19, 2014 is one day of my life that I will never forget. It is the day when I sold the 50th copy of my first ebook.
I didn’t have many resources when I started writing the book. I didn’t have any influential friends, money or experience. All I had was 67 people on my email list. Worst of all, I felt I wasn’t even qualified to write a book.
I now understand that it is possible to make something people want, even if you don’t feel like you are an expert on the subject.
I’m consolidating this valuable learning experience into an article, which I am sharing with you now.
Responsive websites have became increasingly important over the years. Unfortunately, we still need to make older browsers support responsive websites due to various reasons once in a while, and searching around for the correct way of doing it can take up some of your precious time. This article is designed to help you answer the question on supporting responsive websites on older browsers.
I chanced upon heydon’s Codepen for creating self-correcting grids with pseudo classes a while ago and that totally blew my mind away. I started to think about how we can use pseudo selectors to create smarter HTML layouts and I have summarised my thoughts on this in this article.
When I first heard of asymmetric layouts, it was available only in the Singularity GS framework. It sounded incredibly cool and I really wanted to try creating a layout that uses unequal column widths. At that time, I was really happy with Susyone and was reluctant to make the switch.
Imagine my delight when Susy 2 came and it supported asymmetric grids!
In this post, I want to introduce you to asymmetric grids with Susy and show you how easily it can be done.
One question that was asked in the Susy survey I created a month ago really stood out to me. The question is “how to remove margins or paddings of the first and last column without using first-child and last-child in the grid system?”.
This one big question is likely one that has caused huge amounts of headaches to beginners who are just starting to learn about Susy. If we go down into the roots of the question, it is quite likely that you have used the
inside gutter position instead of
after after seeing the many of the tutorials online. To answer this question, you must understand how gutter position affects your layout.
I feel that gutter position is one of the more important settings in Susy because it causes you code things differently when doing your layout. If you have asked this question before, then this blog post about gutter positions is for you.