Style spacing between repeated elements in CSS using flex gap

It's a pretty common scenario - you have to place a few elements in equal distances. E.g. unordered list items.
<ul class="list">
<li class="item"></li>
<li class="item"></li>
<li class="item"></li>
<li class="item"></li>
</div>
The first solution that comes to mind probably is to use margins. Unfortunately - the last element must be styled separately in this case.
.item {
width: 100px;
height: 50px;
margin-bottom: 40px;
}
.item:last-of-type {
margin-bottom: 0;
}
Another idea is to use the basic flex property „space-between” and set a fixed height. There is simple math behind that. Every element has 50px height and between every two of them, we want to have 40px of spacing. 50 * 4 + 40 * 3 = 320.
.list {
display: flex;
flex-direction: column;
justify-content: space-between;
height: 320px;
}
.item {
width: 100px;
height: 50px;
}
The main problem with this solution is the lack of flexibility. By adding a new element to the list - we have to calculate height by hand. Not very cheerful though. (But maybe in your case height of the conatiner is more important for the layout than the specific spacing between elements - then this will be ideal for you).
There is also a third nice option, that I learn and started to use. Flex has property „gap” which is not reserved just to grid as I thought before. It’s a perfect use case for it.
.list {
display: flex;
flex-direction: column;
justify-content: space-between;
row-gap: 40px;
}
.item {
width: 100px;
height: 50px;
}
Work with a team that keeps learning and building better software every day.
Related posts
Dive deeper into this topic with these related posts
You might also like
Discover more content from this category
Sooner or later you'll have to change the null constraint in one of your DB relations. How to do it easily in Ecto?
Sometimes you need to do some database operations at once. A simple example: User-A transfers money to User-B. Updating just one balance at the time creates a risk of data desynchronization. What if the first DB operation goes well but updating the second user’s data fails? Sounds like a hard to catch vulnerability.
People will tell you it's an antipattern, but what if a library needs you to do this?
