Choose CSS features for the problem in front of you
By Gyata Tabiri · Revised November 2, 2026
A newer CSS feature is interesting when it makes a relationship easier to express. Its release date is a weaker reason to change an implementation that already meets the need.
Choose layout around the relationship
Grid is useful for a two-dimensional arrangement; Flexbox often suits a row or column. The decision should follow how the elements need to behave. I would also consider the conventions of an existing project before introducing another layout approach for a single unremarkable section.
Give fluid values something real to respond to
A bounded value such as one expressed with clamp() can help a heading adapt. Its endpoints still need judgment. Try a longer title and inspect the widths between the preferred device presets. A fluid formula can preserve a bad assumption just as efficiently as a fixed value.
Look beyond the declaration
Logical properties can express spacing relative to writing direction, but that alone does not resolve a multilingual layout. Navigation, imagery, directional icons, and content order may also need review. A useful feature addresses part of a problem; it should not be mistaken for a complete solution.
Consider the person inheriting the choice
Browser requirements, existing patterns, and the cost of maintenance belong in the decision. Sometimes a familiar technique makes the intention clearer. Sometimes a newer one removes a fragile workaround. I want to be able to explain which is true for this particular change.
Progress in a stylesheet should be visible in what becomes simpler to express or safer to change. Novelty is welcome when it earns that result.
Read alongside: Judging fluid type through content · Choosing a reusable boundary.
Reference: CSS logical properties.