gallery mixin behave unexpectedly (like the image below) when you’re using Susy?
You’re not alone. Many people have faced the same problems I outlined above. When they meet with these problems, the common question was how to “reset” the output from the
span, or the
gallery mixin, so the weird behavior goes away, but that’s not the best way to fix the problem.
In this article, I’m going to show you why “resetting” is the wrong approach and what you can do instead.
I think it was a few months ago where someone asked me if I had any pointers to help them transit from Bootstrap’s dom-littering
.col classes to either Susy or Neat. It struck me that I haven’t talked about this even though I’ve been using Susy grids for so long!
Anyway, this transition is a fairly big undertaking if you’re doing it for the first time. Allow me to walk you through a four-step process that I use in this article.
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.
This article is here to help you out if you’re having trouble using Masonry with Susy.
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.
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.
When trying to build your layouts with Susy, the first thing you might have tried is to output Susy’s grid background so you can make sure you’re coding the right thing.
I know I did.
But it was tough. I couldn’t figure out that out the first couple of months I used Susy. Even if I did manage to find a way to output the grid, I can’t seem to change the grids when I introduced a change in media queries. It was incredibly frustrating and it was very difficult to learn Susy during that period.
I’d like to share with you one way you can produce as many grid backgrounds and use them with as many breakpoints as you like to.
Sometimes, there is a need to repeatedly declare new layouts as a project goes along. As more layouts gets declared, it can get quite difficult to manage and change these layouts when the need arises.
Because of this, I’ve been toying with the idea of consolidating different kinds of layouts into a sass map and calling the maps with Susy. Thankfully, I managed to hit onto something decent recently. This post shares my method for organizing layouts with Susy
There are times where you might want to use grids that break that certain points instead of using a fully fluid grid. Susy lets you do that easily as well. But first, you’ll need to do a few quick configurations to get that to work.
We went through the very basics of Susy 2 and how it could be used to quickly create very complicated layouts in the previous tutorial on Susy. In this tutorial, we’re going to dive deeper into Susy, and explore how it can be used to develop responsive websites easily.
Susy is a helper tool that lets you created ultra customizable grids on the fly easily.
Its been a while since Susy 2 is officially released. If you loved Susy 1, you will definitely love to use Susy 2 because it offers so much more flexibility.
This is a two part tutorial for Susy 2, and in this tutorial, I will be sharing with you how to create the Complex AG Grid with Susy 2.
We have gone through the absolute basics to Susy in the previous week and looked at how to create complete layout grids simply just by using the span column mixin.
In this post, we’re going to explore other parts of Susy that lets you easily push or pull your content block left or right. I’ll also share with you how responsiveness is built straight into the Susy framework.
Lets begin by looking at some of the padding and margins mixins available to us.
Susy is a plugin to Compass that allows you to create customizable grid frameworks easily. It makes responsive design extremely easy by removing the need to manually calculate widths.
If you need to create repsonsive websites do not want to constrain your design with available frameworks out in the open, Susy might be the perfect answer.
This is the first of a two part tutorial that covers the basics of Susy.
In this tutorial, we are going to install Susy, set up Susy defaults and understand how to create the 10-column complex nested grid AG test found on the susy website.