Circular progress bar
Create an SVG progress bar component
It’s a quite popular way of laying out a content of varying size. Usually a multimedia content, like images, videos or product cards. It makes the media retain it’s original aspect ratio without any distortion or any need to prepare a specific size of an item beforehand.
This type of layout can be achieved through multiple means: using JavaScript libraries for more control, or applying CSS for a basic and more common use case.
As a side note, there’s currently an experimental support for masonry layout in Firefox, that will work on grid container.
To achieve the masonry layout for the most common use case (that is, one item per column), you can simply use the columns
rule, together with its specific property rules for some customisation.
For the HTML, you’ll need a column container, and then just put the elements inside.
<div class="column-container">
<img class="column-item" alt="">
<img class="column-item" alt="">
<img class="column-item" alt="">
</img>
Then style those elements, applying the required rules. In this case, the columns
rule that requires either the ideal number of columns (integer), ideal width of a column (width) or optionally, both of those values.
.column-container {
columns: 3 200px;
}
The effect is already fairly good. The images are properly split into desired amount of columns
With some further customisation, you can achieve better spacing between columns and items, by applying the column-gap
rule on the container, and adding a bottom margin to items.
.column-container {
/* ... */
column-gap: 1rem;
}
.column-item {
margin-bottom: 1rem;
}
Lastly, the layout is already responsive, but you might want to have some more level of control by removing the ideal column count and relying only on the column’s width.
Using the columns
property can be a quick win for some common scenarios, where the order of items is not necessary important or can be managed by the markup. However, when you need to put items in the row order, columns won’t work by themselves, as the content is laid out top-to-bottom first. This will also not be a good solution for cases, when you need to load more content later (for example with infinite scroll).