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.
Susy is a grid layout engine that was built to help web developers create web layouts easily. It allows us to create custom grids and it does its job extremely well.
One of the common complaints about Susy is that it is too simple, it’s only the grid layout engine. There are no UI kits that come with it, and that slows down developers who want to prototype quickly.
The good news is Susy can be integrated into almost any framework or UI kit, including the major ones, like Bootstrap and Foundation.
This is precisely what this tutorial is all about – integrating Susy with another framework, Bootstrap, to be specific. Even if you are not a fan of Bootstrap, you can still glean insights on how to integrate Susy with your UI kit of choice through this tutorial.
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.